-
Notifications
You must be signed in to change notification settings - Fork 16.8k
[stable/jaeger-operator] WATCH_NAMESPACE should be configurable #14968
Comments
Actually an old stale issue about the same problem exists #9298 |
I believe this value should be customizable, as one might want to have multiple operators in the same cluster, each watching different namespaces, like in a multi-tenant scenario. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
Link an old, unmerged PR for reference #9566 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
This issue is being automatically closed due to inactivity. |
Describe the bug
According to jaegertracing/jaeger-operator#60 the value of WATCH_NAMESPACE in
charts/stable/jaeger-operator/templates/deployment.yaml
Lines 41 to 44 in 0007ebb
Version of Helm and Kubernetes:
k8s-v.1.10.6
helm-v2.8.1
Which chart:
[stable/jaeger-operator]
What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
The text was updated successfully, but these errors were encountered: