What is GitOps, and how is it different from a pipeline that runs kubectl apply?
What they are really testing: Whether you understand pull-based reconciliation versus push-based deployment, and can name the concrete benefits rather than treating GitOps as a branding exercise.
A real interview question
What is GitOps, and how is it different from a pipeline that runs kubectl apply?
What most people say
drag me
“GitOps means you keep your Kubernetes YAML in git.”
Everyone keeps YAML in git already. The defining property is continuous reconciliation by an agent that pulls, and without that you have version control, not GitOps.
The follow-ups they ask next
How do you promote a change from staging to production in GitOps?
A commit or pull request against the production path or repository, usually updating an image tag. Promotion becomes a reviewable diff rather than a pipeline parameter.
Someone must hotfix production immediately. What now?
They can change the cluster directly to stop the bleeding, but the agent will revert it, so the fix must land in git quickly. That is a feature: it makes the out-of-band change explicit and temporary.
What the interviewer is listening for
- Defines it as continuous reconciliation
- Names removing cluster credentials from CI
- Acknowledges the operational cost
What sinks the answer
- Says "YAML in git"
- Cannot contrast pull with push
- Presents it as free
If you genuinely do not know
Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.
“GitOps is [an in-cluster agent continuously reconciling reality to a git repo], not just YAML in git. Push-based [applies once and ignores later drift]. The wins are [self-healing drift], [CI needs no cluster credentials], and [git is a truthful deployment log]. The cost is [another component and a less direct feedback loop].”
Keep going with gitops
Mid
Our pipeline takes 45 minutes and developers have stopped waiting for it. How do you fix that?
Mid
A pod is in CrashLoopBackOff after a deploy. Walk me through your debugging, command by command.
Mid
Terraform plan wants to destroy a production database that someone modified manually. What do you do?
Mid
You need to rename a heavily-used database column with zero downtime. How?
Mid
How do you decide CPU and memory requests and limits for a service, and what breaks if you get them wrong?
Mid
The deploy reports success, pods are Running, but users get 502s. Where do you look?
Knowing the answer is not the same as recalling it under pressure
Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.
Start free