* Add a new 'workload name' label override
Today, we have a "workload name" concept that ends up in metrics.
This is defaulted to deriving from deployment metadata (Deployment name,
etc).
This approach is not perfect. We cannot always derive an appropriate
name (for instance, a Pod can be created directly!). WorkloadEntry,
which often is equvilent to Pod, is also using the WE name -- generally
we would want a higher order name there.
To fix this, I propose we add a label to explicitly specify the workload
name. This format mirrors the existing canonical-{service,revision}
label.
* regen
* introduce PROXY annotation
Signed-off-by: Kuat Yessenov <kuat@google.com>
* add release note
Signed-off-by: Kuat Yessenov <kuat@google.com>
* fix
Signed-off-by: Kuat Yessenov <kuat@google.com>
* update api
Signed-off-by: Kuat Yessenov <kuat@google.com>
* rewrite
Signed-off-by: Kuat Yessenov <kuat@google.com>
* rename to proxy_protocol
Signed-off-by: Kuat Yessenov <kuat@google.com>
* make gen
Signed-off-by: Kuat Yessenov <kuat@google.com>
---------
Signed-off-by: Kuat Yessenov <kuat@google.com>
subzone: has been around for a while. It's tested and I believe some folks are using it in production. Probably at least beta.
network: fundamental label used by multicluster in particular for configuring multi-network scenarios. Since multicluster as a feature is beta, it makes sense that the stability here matches.
Keeping the existing labels.go for now until the main code branch is migrated over to use the new variables.
Will also remove security.istio.io/tlsMode (which always was a label, not an annotation) from annotations once the main code branch is migrated over to the label variable.
* add label for assigning a pod's network
* cluster label
* use an annotation instead
* Revert "use an annotation instead"
This reverts commit 24ead1188cdb5675b35fe842545e4f5e5bb35700.
* remove cluster for now
* clarify comment
Mitch Connors