Summary
The controller ConfigMap name was hardcoded to argo-rollouts-config with no way to override it at runtime. Therefore, when running multiple controller instances in the same namespace, there is currently no way to have fully independent set of objects for each controller.
Proposal is to a --configmap-name flag to the argo-rollouts-controller binary so operators can specify an alternative name.
Use Cases
When would you use this?
Example is: deploying multiple controllers in single namespace, with different --instance-id to manage different rollouts.
Message from the maintainers:
Need this enhancement? Give it a 👍. We prioritize the issues with the most 👍.
Summary
The controller ConfigMap name was hardcoded to argo-rollouts-config with no way to override it at runtime. Therefore, when running multiple controller instances in the same namespace, there is currently no way to have fully independent set of objects for each controller.
Proposal is to a
--configmap-nameflag to the argo-rollouts-controller binary so operators can specify an alternative name.Use Cases
When would you use this?
Example is: deploying multiple controllers in single namespace, with different
--instance-idto manage different rollouts.Message from the maintainers:
Need this enhancement? Give it a 👍. We prioritize the issues with the most 👍.