ArgoCD and FluxCD are the two dominant GitOps engines for Kubernetes — this breakdown tells you exactly which one to pick and why.
Set the sync option SkipDryRunOnMissingResource=true and add the 'helm.sh/resource-policy: keep' annotation to CRD manifests. Alternatively, manage CRDs in a separate ArgoCD Application with pruning disabled so application syncs never touch cluster-scoped CRD resources.
Flux compares the applied manifest against the live object using server-side apply. If a mutating webhook modifies fields not present in the Git source, Flux will attempt to revert them on the next reconciliation cycle. Exclude webhook-managed fields using Flux's .spec.ignore patch rules to prevent reconciliation loops.
Discussion0