Skip to content

Advanced: GitOps to Kubernetes

This track levels delivery up to GitOps. Instead of pushing changes into a cluster, you make Git the single source of truth, and let Argo CD keep the cluster continuously in sync. This is where the delivery pillar meets Kubernetes.

You will learn how to:

  • Explain what GitOps is and why it pulls rather than pushes
  • Describe your app as Kubernetes manifests in Git
  • Install and use Argo CD
  • Deploy automatically from Git, and close the full commit-to-cluster loop
  • Let the cluster heal itself when it drifts
  • Recognise safer rollout strategies like canary and blue-green

Prerequisites

You should have:

Tutorials

  • What is GitOps?

    Git as the single source of truth, and the reconciliation loop.

    Start Tutorial

  • Push vs Pull Delivery

    Why GitOps pulls, and why that is safer.

    Start Tutorial

  • Snapshot on Kubernetes

    Write the manifests that describe the app as desired state.

    Start Tutorial

  • Install Argo CD

    Add the GitOps agent to your cluster.

    Start Tutorial

  • Your First Synced App

    Point Argo CD at your repo and watch it deploy Snapshot.

    Start Tutorial

  • Closing the Loop

    A new image flows from CI all the way to the cluster automatically.

    Start Tutorial

  • Drift and Self-Healing

    Change the cluster by hand, and watch Argo CD put it back.

    Start Tutorial

  • Progressive Delivery

    Safer rollouts with canary and blue-green.

    Start Tutorial

  • Capstone: Full GitOps Loop

    From a commit to a self-healing deployment, end to end.

    Start Capstone

When you finish, you have completed the full path: build with Docker, orchestrate with Kubernetes, and deliver with CI/CD and GitOps.