Kubernetes and Cloud Native Associate (KCNA)Cloud Native ArchitectureMedium
A cloud-native application relies on a configuration management system where the desired state of the entire system (infrastructure, applications, and configurations) is declared in Git. An automated process continuously observes the live system's actual state and compares it to the desired state in Git, automatically applying any necessary changes to bring the system into conformance. What is this automated process specifically called?
- AContinuous Integration
- BCanary Deployment
- CReconciliation
- DContinuous Delivery
Show answer & explanationAnswer & explanation
Correct answer: C. Reconciliation
Reconciliation is the core process in GitOps where an operator continuously observes the actual state of the system and compares it to the desired state declared in Git, then acts to converge the two.
Why the other options are wrong
- A. Continuous Integration (CI) focuses on merging code changes and running automated tests, not comparing live state to a Git-defined desired state.
- B. Canary Deployment is a release strategy that gradually rolls out a new version of an application to a small subset of users, not the state synchronization process itself.
- D. Continuous Delivery (CD) automates the release process to production, but 'reconciliation' describes the specific mechanism of state synchronization in GitOps.
Reconciliation (GitOps)
In GitOps, reconciliation is the automated process by which a system continuously observes its current state, compares it to a desired state defined in Git, and then takes action to make the current state match the desired state.
- Core mechanism for maintaining desired state in GitOps.
- Performed by an automated operator or controller.
- Ensures the deployed system always matches the Git repository.
Memory trick: Git's Desired State Is Reconciled Constantly.