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
We have installed the jaeger operator as a cluster-specific component and the agents are deployed in the individual namespace.
While injecting the sidecar into the new namespace the application deployment pods were labeled with the old namespace details.
Below is the label for the namespace (namespace1)
app.kubernetes.io/name=aplication-manager-api-server
app.kubernetes.io/part-of=aplication
**sidecar.jaegertracing.io/injected=namespace2-jaeger-test-jaeger-jaeger** -> 2nd namespace label
managed-by=helm
system-id=namespace1 -> jaeger deploying into the 1st namespace
PS::--- Whenever we are enabling jaeger into the second namespace still the jaeger deployment is referring to the 1st namespace of query label.
Steps to reproduce
We have installed the jaeger operator as a cluster-specific component and the agents are deployed in the individual namespace.
While injecting the sidecar into the new namespace the application deployment pods were labeled with the old namespace details.
Below is the label for the namespace (namespace1)
app.kubernetes.io/name=aplication-manager-api-server
app.kubernetes.io/part-of=aplication
**sidecar.jaegertracing.io/injected=namespace2-jaeger-test-jaeger-jaeger**
managed-by=helm
system-id=namespace1
Whenever we are enabling jaeger into the second namespace still the jaeger deployment is referring to the 1st namespace query label.
Expected behavior
The label should be mapped correctly
Relevant log output
No response
Screenshot
No response
Additional context
No response
Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs
No response
The text was updated successfully, but these errors were encountered:
What happened?
We have installed the jaeger operator as a cluster-specific component and the agents are deployed in the individual namespace.
While injecting the sidecar into the new namespace the application deployment pods were labeled with the old namespace details.
Below is the label for the namespace (namespace1)
PS::--- Whenever we are enabling jaeger into the second namespace still the jaeger deployment is referring to the 1st namespace of query label.
Steps to reproduce
We have installed the jaeger operator as a cluster-specific component and the agents are deployed in the individual namespace.
While injecting the sidecar into the new namespace the application deployment pods were labeled with the old namespace details.
Below is the label for the namespace (namespace1)
Expected behavior
The label should be mapped correctly
Relevant log output
No response
Screenshot
No response
Additional context
No response
Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs
No response
The text was updated successfully, but these errors were encountered: