Reconciliation loops are the beating heart of GitOps and Kubernetes: read desired state, read actual state, compute the diff, apply corrections, repeat forever. It's a beautiful model — until you have two loops reconciling the same resource with different opinions. Then you get a fight that never ends, burns CPU, and makes your dashboards flicker.

The pattern shows up whenever ownership is ambiguous. Classic scenarios:

• Overlapping controllers: Argo CD reconciles a Deployment to replicas: 3, while HPA reconciles it to replicas: 7 based on CPU. Every 30 seconds they overwrite each other.
• Operator vs Helm: A cert-manager Certificate CR sets tls.crt in a Secret; a Helm chart's post-install hook also writes to that Secret. Both loops "correct" the other's write.
• Human vs automation: An engineer kubectl edits a ConfigMap to debug prod. Flux notices the drift 60 seconds later and reverts it — mid-investigation.

Real example: A team ran Argo CD syncing a Deployment manifest with replicas: 2, and HPA scaling between 2 and 20. During a traffic spike HPA scaled to 15. Argo's next sync (every 3 minutes) scaled it back to 2. Latency spiked, HPA scaled up again, Argo scaled down. The oscillation lasted 40 minutes before someone noticed pods being killed mid-request. Fix: remove replicas from the manifest entirely, or add ignoreDifferences for that field in the Argo Application spec. Ownership must be exclusive per field, not per resource.

Rule of thumb: for any writable field on any resource, exactly one controller owns it. Zero owners means drift accumulates; two or more owners means a fight. Kubernetes 1.22+ made this explicit with Server-Side Apply field ownership — each manager claims specific fields, and conflicting writes error out instead of silently thrashing. Use it.

How to detect the fight: if the resourceVersion of an object increments faster than any human is touching it — say, more than 10 changes per hour with no deployment — two controllers are almost certainly wrestling. Check metadata.managedFields to see who's writing what.

Design defenses:

• Split responsibility by field, not by resource. Argo owns image tag; HPA owns replica count.
• Use ignoreDifferences (Argo) or --server-side --force-conflicts deliberately — never as a shortcut.
• Set reconciliation intervals asymmetrically so oscillations damp rather than resonate.
• Alert on high resourceVersion churn per object; it's the earliest signal of a loop war.