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
Is your feature request related to a problem? Please describe.
If I have grafana labs deployments in multiple namespaces I also need to deploy the rollout-operator multiple times. This is inefficient and unlike any other k8s operators that are generally employed.
Describe the solution you'd like
Having the rollout operator optionally be capable of working across all namespaces.
Describe alternatives you've considered
Deploying the operator into every namespace, this is inefficient and introduces complexity.
The text was updated successfully, but these errors were encountered:
I'm not sure we will ever do this. Binding 1 rollout-operator to 1 namespace was a specific design decision to keep it simpler and isolated from other instances.
This is inefficient
Why do you consider it inefficient? The rollout-operator is very lightweight.
Is your feature request related to a problem? Please describe.
If I have grafana labs deployments in multiple namespaces I also need to deploy the rollout-operator multiple times. This is inefficient and unlike any other k8s operators that are generally employed.
Describe the solution you'd like
Having the rollout operator optionally be capable of working across all namespaces.
Describe alternatives you've considered
Deploying the operator into every namespace, this is inefficient and introduces complexity.
The text was updated successfully, but these errors were encountered: