Kubernetes and Cloud Native Associate (KCNA)Cloud Native DeliveryHard
A team is using Git to manage their application code and Kubernetes manifests. They want to implement a workflow where the entire state of their Kubernetes cluster is described declaratively in Git, and any changes in Git are automatically applied to the cluster, while also ensuring the cluster's actual state never drifts from the Git-defined desired state. What is this operational model called?
- AGitOps
- BTrunk-based development
- CFeature branching
- DShift-left testing
Show answer & explanationAnswer & explanation
Correct answer: A. GitOps
GitOps is an operational framework that takes DevOps best practices used for application development (like version control, collaboration, CI/CD) and applies them to infrastructure automation. It uses Git as the single source of truth for declarative infrastructure and applications, with automated tools to reconcile the actual state with the desired state in Git.
Why the other options are wrong
- B. Trunk-based development is a branching strategy, not an operational model for infrastructure.
- C. Feature branching is a branching strategy, not an operational model.
- D. Shift-left testing is a testing methodology, not an operational model for cluster state management.
GitOps
An operational framework that uses Git as the single source of truth for declarative infrastructure and applications. Changes to the desired state in Git are automatically applied to the target environment, and reconciliation ensures actual state matches desired state.
- Git is the single source of truth for declarative configurations.
- Automated agents continuously reconcile the cluster's actual state with Git's desired state.
- Provides an audit trail for all changes to infrastructure and applications.
- Enables faster deployments, easier rollbacks, and self-healing systems.
Memory trick: GitOps is like a 'Git-powered autopilot' for your cluster.