GitOps Reconciliation

This is the cluster’s central runtime scenario: it implements [MT01 GitOps Administration] and, together with selfHeal, protects [RE01 24/7 Availability] against configuration drift.

Argo CD reconciling a Git commit onto the cluster, including automatic drift correction.
Figure 1. Argo CD reconciling a Git commit onto the cluster, including automatic drift correction.
Motivation

Every add-on in pandur/ is reconciled this way. Because automated.selfHeal and automated.prune are enabled cluster-wide, a manual kubectl change is reverted automatically on the next reconciliation loop (typically within a few minutes), which is what makes [MT01 GitOps Administration] and [CO-001 Small Team ] achievable for a very small team: there is exactly one way to change the cluster, and it is self-enforcing.

Retry behavior

Failed syncs are retried with an exponential backoff (duration: 5s, factor: 2, up to maxDuration: 3m, limit: 10 — see any pandur/apps/*.yml), so transient errors (e.g. a webhook race, a temporarily unavailable admission webhook) do not require manual intervention.