What is the basic principle of GitOps?
WHAT IT TESTS: declarative continuous delivery. OUTLINE: Git holds desired state; a controller continuously reconciles the cluster to match it; benefits are auditability, rollback, and drift correction. RED FLAG: describing push-based scripts as GitOps.
WHAT IT TESTS: whether you understand declarative, pull-based delivery. ANSWER OUTLINE: in GitOps the entire desired state of the system is declared in a Git repository, which is the single source of truth; an in-cluster controller continuously compares live state to Git and reconciles any difference. Git being authoritative gives you version history, code review, easy rollback by revert, and automatic drift correction. RED FLAG: calling any kubectl-from-CI pipeline GitOps, or omitting the continuous reconciliation loop.
Read the original → interview
- #gitops
- #kubernetes
- #declarative
- #argocd
- #flux
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.