You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would also be useful is the ability to set a custom label on the Jaeger Operator pods while using the standard chart. My organization uses labels to associate standardized network policies (e.g. API server access, DNS access) with pods. Jaeger Operator requires API server access to function. Without the ability to set one of our existing labels on its pods, we have to create a custom network policy to grant it this access rather than use our existing API server access network policy. This complicates compliance.
For example, it would be good to be able to specify a custom label like this:
And then have it show up on the Jaeger Operator pod:
$ kubectl get pod -oyaml jaeger-operator-555-555 | grep labels -A2
labels:
api-server-access: "true"
app.kubernetes.io/name: jaeger-operator
The text was updated successfully, but these errors were encountered:
leonsp-ai
changed the title
Custom labels for Jaeger Operator itself
[jaeger-operator] Custom labels for Jaeger Operator pods in the chart
Jun 29, 2020
It's great that Jaeger Operator supports custom labels for all-in-one and other pods: jaegertracing/jaeger-operator#445
What would also be useful is the ability to set a custom label on the Jaeger Operator pods while using the standard chart. My organization uses labels to associate standardized network policies (e.g. API server access, DNS access) with pods. Jaeger Operator requires API server access to function. Without the ability to set one of our existing labels on its pods, we have to create a custom network policy to grant it this access rather than use our existing API server access network policy. This complicates compliance.
For example, it would be good to be able to specify a custom label like this:
And then have it show up on the Jaeger Operator pod:
The text was updated successfully, but these errors were encountered: