Core

GitOps: reconciliation, not deployment

GitOps is the Kubernetes control loop applied to your deployments: a controller compares live resources to versioned desired state and reconciles configured differences. The distinction from a pipeline that runs kubectl apply is not tooling preference. It changes what happens when someone edits the cluster directly, and it changes who holds cluster credentials.

a free account opens the core tier · no card

RELATED CONCEPTS

The control loop: the one idea Kubernetes is built on State and drift: why infrastructure as code needs a ledger

PRACTICE THIS IN REAL QUESTIONS

CI/CD, Release Engineering & GitOpsPush or pull for deployments? Explain what pull actually removes from your threat model.→CI/CD, Release Engineering & GitOpsA teammate kubectl-applied a fix during an incident and Argo CD reverted it a minute later. What happened?→CI/CD, Release Engineering & GitOpsOur Argo CD setup has forty services and grows every quarter. How should we organise Applications?→CI/CD, Release Engineering & GitOpsTwelve clusters across three regions take every release. How do you stage the rollout so one bad build cannot hit everywhere?→Infrastructure as Code & ConfigurationEveryone does GitOps for Kubernetes. Can the same model govern plain cloud infrastructure, and what breaks in translation?→Containers & KubernetesYou are at twelve clusters and adding two a quarter. How do you stop each one becoming a snowflake?→