Skip to content

CGOA - Certified GitOps Associate

Multiple-choice exam | 90 minutes | Passing score: 75% | $250 USD

The CGOA (Certified GitOps Associate) validates your understanding of GitOps principles, patterns, and related practices. It’s a theory exam — multiple-choice questions, no terminal access. Think of it as “KCNA for GitOps.”

KubeDojo covers ~90%+ of CGOA topics through our existing Platform Engineering track. This page maps CGOA domains to existing modules so you can prepare efficiently.

Good news: If you’ve already worked through our GitOps discipline and toolkits, you’ve covered the hardest parts. This exam tests understanding of concepts, not hands-on skills — but our hands-on modules give you the deep understanding that makes theory questions easy.


DomainWeightKubeDojo Coverage
GitOps Terminology20%Excellent (GitOps discipline modules)
GitOps Principles30%Excellent (GitOps discipline + IaC modules)
Related Practices16%Excellent (IaC, DevOps, CI/CD, DevSecOps modules)
GitOps Patterns20%Excellent (promotion, drift, progressive delivery modules)
Tooling14%Excellent (ArgoCD, Flux, Helm, Kustomize toolkit modules)

  • Continuous delivery and deployment concepts
  • Declarative vs imperative approaches
  • Desired state and state stores
  • Drift detection and correction
  • Reconciliation loops
ModuleTopicRelevance
GitOps 3.1What is GitOps? OpenGitOps 4 principles, key terminologyDirect
GitOps 3.4Drift detection and reconciliation loopsDirect
IaC 6.1Declarative vs imperative, desired state conceptsDirect
IaC 6.5Drift remediation strategiesDirect
Modern DevOps: GitOpsGitOps overview for beginnersSupporting

  • Declarative: Desired state is expressed declaratively
  • Versioned and Immutable: Desired state is stored in a versioned, immutable source of truth
  • Pulled Automatically: Agents pull desired state automatically
  • Continuously Reconciled: Agents continuously observe and reconcile actual state

This is the highest-weighted domain. Know the OpenGitOps v1.0 principles cold.

ModuleTopicRelevance
GitOps 3.1OpenGitOps 4 principles in depthDirect
GitOps 3.2Git as the versioned, immutable source of truth; repo strategiesDirect
GitOps 3.4Continuous reconciliation and drift detectionDirect
GitOps 3.6Pull-based delivery across clustersDirect
IaC 6.1Declarative configuration, state managementDirect
ArgoCDPull-based reconciliation in practice (Application CRD, sync policies)Direct
FluxPull-based reconciliation with 5 controllersDirect

  • Configuration as Code (CaC)
  • Infrastructure as Code (IaC)
  • DevOps culture and practices
  • CI/CD pipelines and their relationship to GitOps
ModuleTopicRelevance
IaC 6.1IaC fundamentals, declarative infrastructureDirect
IaC 6.4IaC at scale, configuration managementDirect
IaC 6.2Testing infrastructure codeSupporting
IaC 6.3Security in IaCSupporting
Modern DevOps: IaCIaC overview for beginnersSupporting
Modern DevOps: CI/CDCI/CD pipeline fundamentalsDirect
Modern DevOps: DevSecOpsDevOps/DevSecOps cultureSupporting
DevSecOps 4.3CI/CD pipeline design and security integrationSupporting
Cloud Native EcosystemCNCF landscape, cloud native practicesSupporting
DaggerModern CI/CD pipeline designSupporting
TektonK8s-native CI/CDSupporting

  • Deployment and release patterns (blue-green, canary, rolling)
  • Progressive delivery strategies
  • Pull-based vs event-driven reconciliation
  • Environment promotion strategies
  • Repository patterns (monorepo, polyrepo)
ModuleTopicRelevance
GitOps 3.2Monorepo vs polyrepo, app-of-apps patternDirect
GitOps 3.3Environment promotion patterns (dev/staging/prod)Direct
GitOps 3.5Secrets management patterns in GitOps workflowsDirect
GitOps 3.6Multi-cluster deployment patternsDirect
Argo RolloutsProgressive delivery: canary, blue-green, analysis runsDirect
ArgoCDApplicationSet, sync waves, hooks, pull-based modelDirect
FluxEvent-driven reconciliation, notification controllerDirect
Helm & KustomizeManifest customization patterns for promotionDirect

  • Manifest formats (YAML, JSON, Helm charts, Kustomize overlays)
  • State store management (Git repositories)
  • Reconciliation engines (ArgoCD, Flux)
ModuleTopicRelevance
ArgoCDApplication CRD, sync policies, RBAC, ApplicationSetDirect
FluxGitRepository, HelmRelease, Kustomization, 5 controllersDirect
Helm & KustomizeHelm charts, Kustomize overlays, manifest packagingDirect
GitOps 3.2Git as state store, repo layout patternsDirect
Argo RolloutsProgressive delivery toolingDirect

CGOA PREPARATION PATH (recommended order)
══════════════════════════════════════════════════════════════
Week 1: GitOps Foundations (covers Domains 1 + 2 = 50% of exam!)
├── GitOps 3.1 — What is GitOps, OpenGitOps principles
├── IaC 6.1 — Declarative vs imperative, desired state
├── GitOps 3.4 — Drift detection & reconciliation
└── IaC 6.5 — Drift remediation strategies
Week 2: GitOps Patterns (Domain 4 = 20%)
├── GitOps 3.2 — Repository strategies (monorepo vs polyrepo)
├── GitOps 3.3 — Environment promotion patterns
├── GitOps 3.5 — Secrets management in GitOps
└── GitOps 3.6 — Multi-cluster GitOps
Week 3: Tooling Deep Dive (Domain 5 = 14%)
├── ArgoCD toolkit module (pull-based reconciliation)
├── Flux toolkit module (event-driven reconciliation)
├── Helm & Kustomize (manifest formats)
└── Argo Rollouts (progressive delivery)
Week 4: Related Practices + Review (Domain 3 = 16%)
├── Modern DevOps: CI/CD pipelines
├── IaC 6.2-6.4 (testing, security, scale)
├── DevSecOps 4.3 (security in CI/CD)
└── Review all domains, focus on terminology

Pro tip: Domains 1 and 2 together are worth 50% of the exam and are both covered by the same set of modules. Nail the OpenGitOps principles and terminology first — it’s the highest ROI study time.


  • This is a theory exam — no terminal, no kubectl. You need to understand concepts, not execute them. But our hands-on modules build deeper understanding than reading alone.
  • Know the 4 OpenGitOps principles by heart — Declarative, Versioned & Immutable, Pulled Automatically, Continuously Reconciled. Expect multiple questions testing nuances of each.
  • Pull vs push is a key distinction — understand why pull-based (agent in cluster polling Git) is the GitOps way, and how event-driven (webhook triggers) differs.
  • ArgoCD vs Flux — know the architectural differences (single controller vs 5 specialized controllers), not just that both “do GitOps.”
  • Progressive delivery is not the same as CI/CD — canary/blue-green/rolling are release strategies, separate from the build/test pipeline.
  • Declarative != YAML — declarative is about expressing what not how. The exam may test this distinction.
  • 90 minutes is generous — for ~60 multiple-choice questions, you have ~1.5 min per question. Flag and skip anything you’re unsure about.
  • 75% pass rate — you can miss roughly 1 in 4 questions. Don’t panic over a few unknowns.

KubeDojo’s existing Platform Engineering track covers the vast majority of CGOA topics. Here’s what’s left:

TopicStatusNotes
OpenGitOps specification detailsFully coveredGitOps 3.1 covers all 4 principles from the official spec
Configuration as Code (CaC) vs IaC distinctionMinor gapIaC modules cover IaC deeply; CaC as a distinct concept (e.g., application config vs infrastructure) is not explicitly called out but is implicitly covered
GitOps history and originMinor gapGitOps 3.1 likely covers Weaveworks/Alexis Richardson origin, but exam may ask specific historical details
Comparison of push vs pull CD modelsCoveredGitOps 3.1 + ArgoCD/Flux modules contrast the models
YAML/JSON/Jsonnet manifest formatsCoveredHelm & Kustomize module covers YAML and Helm; Jsonnet is briefly covered in the Helm/Kustomize module

No new modules are needed. The 6 GitOps discipline modules, 4 GitOps toolkit modules, 6 IaC modules, and supporting prerequisites/CI-CD modules provide comprehensive CGOA preparation.


CERTIFICATION PATH
══════════════════════════════════════════════════════════════
Associate Level:
├── KCNA (Cloud Native Associate) — K8s fundamentals
├── KCSA (Security Associate) — Security fundamentals
└── CGOA (GitOps Associate) ← YOU ARE HERE
Professional Level:
├── CKA (K8s Administrator) — Cluster operations
├── CKAD (K8s Developer) — Application deployment
├── CKS (K8s Security Specialist) — Security hardening
└── CNPE (Platform Engineer) — Full platform skills
Specialist (Coming):
└── CKNE (K8s Network Engineer) — Advanced networking

The CGOA pairs naturally with the KCNA — together they cover Kubernetes fundamentals and GitOps delivery. If you’re pursuing the full Kubestronaut path, CGOA knowledge directly supports the CKA (deployments, rollouts) and CNPE (GitOps is 25% of that exam).