Push vs Pull Model

Push vs Pull Model A workflow diagram generated by Archify. 01 / Push model · traditional CI/CD 02 / Pull model · GitOps (recommended) CI Pipeline · cluster credentials · Push model · traditional CI/CD · outside cluster CI Pipeline cluster credentials outside cluster Cluster · changes pushed in · Push model · traditional CI/CD Cluster changes pushed in Git Repo · desired state · Pull model · GitOps (recommended) · source of truth Git Repo desired state source of truth GitOps Agent · inside the cluster · Pull model · GitOps (recommended) · reconciles GitOps Agent inside the cluster reconciles Cluster · actual state · Pull model · GitOps (recommended) Cluster actual state kubectl apply watch apply Legend Automation (CI pipeline / GitOps agent) Git repository Kubernetes cluster

Push Model Disadvantages

  • • Requires cluster credentials in the CI system
  • • Harder to audit who made changes
  • • No automatic drift detection

Pull Model Advantages

  • • Enhanced security (no external credentials)
  • • Complete audit trail in Git
  • • Automatic drift detection and correction
  • • Works behind firewalls