Kubernetes and Cloud Native Associate (KCNA)Cloud Native ArchitectureHard
A cloud-native application relies on a configuration management system where desired state is stored in version-controlled Git repositories. An in-cluster agent continuously observes the actual state of the cluster and compares it with the desired state in Git, automatically applying any discrepancies. This 'pull-based' approach, where changes are detected and applied from within the cluster, is a defining characteristic of which operational model?
- AInfrastructure as Code (IaC)
- BDevOps
- CContinuous Delivery
- DGitOps
Show answer & explanationAnswer & explanation
Correct answer: D. GitOps
GitOps is an operational model that uses Git as the single source of truth for declarative infrastructure and applications. It relies on an in-cluster agent to continuously reconcile the actual state with the desired state defined in Git, using a 'pull-based' mechanism.
Why the other options are wrong
- A. IaC is a foundational concept (defining infrastructure with code) but doesn't specify the 'pull-based' reconciliation mechanism that GitOps uses.
- B. DevOps is a culture and set of practices, not an operational model specific to Git-driven cluster management.
- C. Continuous Delivery is a practice of making software ready for release, not a specific operational model for managing infrastructure state from Git.
GitOps
An operational framework that takes DevOps best practices like version control, collaboration, compliance, and CI/CD, and applies them to infrastructure automation, using Git as the single source of truth for declarative infrastructure and applications.
- Git is the single source of truth.
- Declarative configurations.
- Automated reconciliation (pull-based).
- Enables auditable, repeatable deployments.
Memory trick: GitOps is like a gardener tending the cluster, always checking the master blueprint in Git.