Kubernetes and Cloud Native Associate (KCNA)Cloud Native DeliveryMedium
A team is using Git to manage their application code and Kubernetes manifests. They want to ensure that all changes to the production environment are made exclusively through Git commits and pull requests, and that the actual state of the cluster continuously converges with the desired state defined in Git. Which operational model are they following?
- AWaterfall Model
- BGitOps
- CFeature Branching
- DTrunk-Based Development
Show answer & explanationAnswer & explanation
Correct answer: B. GitOps
GitOps is an operational framework that takes DevOps best practices like version control, collaboration, and CI/CD, and applies them to infrastructure automation. It uses Git as the single source of truth for declarative infrastructure and applications.
Why the other options are wrong
- A. The Waterfall Model is a linear software development process, completely unrelated to modern cloud-native operational models.
- C. Feature Branching is a strategy where features are developed on separate branches, also not an operational model for cluster state.
- D. Trunk-Based Development is a branching strategy emphasizing frequent merges to a single main branch, not an operational model for cluster state.
GitOps
GitOps is an operational framework that uses Git as the single source of truth for declarative infrastructure and applications, enabling automated deployment and continuous reconciliation.
- Git is the single source of truth for desired state.
- Declarative specifications for infrastructure and applications.
- Automated reconciliation of actual state to desired state.
- Uses familiar Git tools (PRs, commits) for operations.
Memory trick: GitOps is like a 'Git-powered autopilot' for your Kubernetes cluster.