All 28 GitOps Principles questions
More in GitOps Principles
What is GitOps? What are the core principles of GitOps? How does ArgoCD implement GitOps? What is declarative vs imperative configuration? What is a source of truth and why does GitOps use Git for it? What is continuous reconciliation? What tools implement GitOps besides ArgoCD? What is idempotency and why does it matter in GitOps? What is configuration drift and how does GitOps handle it? What are the benefits of GitOps over traditional deployment approaches?
Advertisement
Back to results for “GitOps Principles”
ArgoCD › GitOps Principles

What is the difference between push-based and pull-based deployment?

Beginner

Answer

In push-based CD, an external pipeline (e.g., Jenkins) has cluster credentials and pushes changes into the cluster. In pull-based GitOps, an in-cluster agent pulls the desired state from Git and applies it. Pull-based keeps credentials inside the cluster, reduces attack surface, and continuously reconciles rather than firing once per pipeline run.
Real-world example Instead of the CI server holding kubeconfig secrets, ArgoCD inside the cluster pulls manifests from Git, so CI never touches the cluster.

Common follow-ups: Why is pull-based more secure? | Can you combine CI with GitOps CD?

Multi-cluster Applications GitOps Principles
All 28 GitOps Principles questions