Use Case

Application is deployed to hundreds of instances for different customers, each has different configuration. Code based is stable, not frequently change. Following tools are used:

• Multi tenant approach can not be considered.
• Application is packed as container image.
• Kubernetes environment, strictly protected, no access to cluster admin privileges.
• Application is deployed with Helm Charts and Azure DevOps pipeline
• Each prod environments has slightly different configuration, like secrets, ConfigMap, K8s resources.

Question and Discussion

Normal CI/CD process is for application development, with frequent code change and one final destination which is prod env.
But is there a standard practice, tools set for deploying and managing one application to hundreds of different prod environments?
Managing one Application instance at a time is currently used, but it is not very GitOps in my opinion, and also not efficient for hundreds of instances.

I found ArgoCD is quite closed for the use case, with IaC pull approach, but can not be used because it needs cluster-admin privilege. (https://argo-cd.readthedocs.io/en/stable)

Overview