A platform team uses ArgoCD and needs to manage dev, staging, and production environments with environment-specific configuration but a shared application chart. Which approach is most consistent with GitOps principles?

Question

Accepted Answer

B. Store environment-specific configuration as Kustomize overlays or Helm values files in Git, with separate ArgoCD Applications pointing to each environment path. Storing environment-specific configuration as Kustomize overlays or Helm values files in Git, with separate ArgoCD Applications targeting each path, is the recommended GitOps multi-environment pattern. All configuration is in Git and environments can be promoted independently through PR merges. Option d violates the GitOps principle of Git as the source of truth because configuration is not stored in Git.

A platform team uses ArgoCD and needs to manage dev, staging, and production environments with environment-specific configuration but a shared application chart. Which approach is most consistent with GitOps principles?

Related Questions

Discussion