argocd-helm-eso-setups

What problem does it solve?

Diagnoses and resolves ownership and reconciliation conflicts in GitOps environments where ArgoCD, Helm, and the ExternalSecrets Operator (ESO) coexist, preventing silent divergence and repetitive rollbacks caused by mixed ownership markers, selfHeal behavior, and fixed-name collisions.

Core Features & Use Cases

• Ownership mapping and conflict diagnosis across ArgoCD, Helm, and ESO to determine which tool owns a resource and why it is contested.
• Guidance for transferring ownership between Helm and ArgoCD, including adopting Helm-managed resources into ArgoCD and reassigning responsibility back to Helm when appropriate.
• Decision-tree guidance for when to modify git state versus kubectl patches, with emphasis on selfHeal semantics and pruning behavior in mixed environments.
• ESO-specific considerations, including how to interpret ESO integration issues and how to render or escape template expressions within Helm charts to avoid data leakage or misrendering.
• Real-world workflows and governance patterns to maintain predictable, auditable changes across charts, releases, and external secret provisioning.

Quick Start

Review a representative resource with kubectl and argocd to identify ownership markers, then update the Git repository to reflect the desired ownership before syncing.