Opscraft
Kubernetes, EKS, GitOps & releases

GitOps with Flux & Argo CD

New6 lessons · 24 min · 3 tests ·

GitOps is how most modern Kubernetes platforms deploy: Git holds the desired state and an in-cluster controller continuously reconciles the cluster to it. Running Flux in production is a real strength — interviews will test whether you understand it beyond "it syncs Git", and will often ask you to compare it with Argo CD, design a multi-cluster repo layout, handle secrets, promote between environments, automate image updates, and recover from failures.

Stage 3 · Production platforms

Know these first

After this topic you can

  • Explain pull-based GitOps and why it helps
  • Run Flux or Argo CD to sync clusters from Git
  • Promote changes across environments and handle secrets

Lessons

  1. 1GitOps principles 3 min read
    • The four principles (OpenGitOps)
    • Push vs pull deployment
  2. 2Flux in depth 7 min read
    • Architecture: the GitOps Toolkit
    • Bootstrap
    • Sources
    • Kustomizations: apply, prune, health, order
    • Operating Flux
    • Multi-tenancy in Flux
  3. 3Argo CD in depth 4 min read
    • Architecture
    • Application
    • Flux vs Argo CD
  4. 4Repository design and promotion 3 min read
    • Typical layout (monorepo)
    • Promotion
    • Progressive delivery
  5. 5Secrets, security and operations 4 min read
    • Secrets in GitOps
    • Security of the GitOps pipeline
    • Troubleshooting
  6. 6Interview questions and model answers 3 min read
    • "What is GitOps and why use it over CI pushing to the cluster?"
    • "Explain how Flux deploys a change end to end."
    • "Flux or Argo CD?"
    • "How do you promote between environments?"
    • "How do you handle secrets in GitOps?"
    • "Someone needs an emergency hotfix directly in the cluster. What happens?"
    • "A teammate deleted a folder in the GitOps repo and production services vanished. What now?"