GitOps Solution: Intermediate (EN)

This solution guide belongs to the assessment Intermediate. It does not provide one rigid answer; it defines verifiable answer criteria.

Grading Rubric

Area	Expectation
Principles	Declarative, versioned, automatically pulled and continuously reconciled are applied correctly.
Evidence	Answers name source, commit, rendering, controller and status evidence.
Operations	Drift, promotion, rollback, multi-tenancy and observability are covered.
Security	Secrets, RBAC, policy, signatures and supply chain are assessed.

Sample Criteria

Solution 01: Kustomize

A strong answer for Kustomize names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 02: Helm

A strong answer for Helm names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 03: Argo CD Applications

A strong answer for Argo CD Applications names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 04: Flux Sources

A strong answer for Flux Sources names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 05: Promotion

A strong answer for Promotion names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 06: Pull Requests

A strong answer for Pull Requests names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 07: Rollbacks

A strong answer for Rollbacks names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 08: Kustomize

A strong answer for Kustomize names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 09: Helm

A strong answer for Helm names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 10: Argo CD Applications

A strong answer for Argo CD Applications names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 11: Flux Sources

A strong answer for Flux Sources names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 12: Promotion

A strong answer for Promotion names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 13: Pull Requests

A strong answer for Pull Requests names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 14: Rollbacks

A strong answer for Rollbacks names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 15: Kustomize

A strong answer for Kustomize names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 16: Helm

A strong answer for Helm names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 17: Argo CD Applications

A strong answer for Argo CD Applications names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 18: Flux Sources

A strong answer for Flux Sources names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 19: Promotion

A strong answer for Promotion names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 20: Pull Requests

A strong answer for Pull Requests names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 21: Rollbacks

A strong answer for Rollbacks names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 22: Kustomize

A strong answer for Kustomize names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 23: Helm

A strong answer for Helm names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 24: Argo CD Applications

A strong answer for Argo CD Applications names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 25: Flux Sources

A strong answer for Flux Sources names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 26: Promotion

A strong answer for Promotion names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 27: Pull Requests

A strong answer for Pull Requests names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 28: Rollbacks

A strong answer for Rollbacks names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 29: Kustomize

A strong answer for Kustomize names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 30: Helm

A strong answer for Helm names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 31: Argo CD Applications

A strong answer for Argo CD Applications names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 32: Flux Sources

A strong answer for Flux Sources names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 33: Promotion

A strong answer for Promotion names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 34: Pull Requests

A strong answer for Pull Requests names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 35: Rollbacks

A strong answer for Rollbacks names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 36: Kustomize

A strong answer for Kustomize names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 37: Helm

A strong answer for Helm names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 38: Argo CD Applications

A strong answer for Argo CD Applications names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 39: Flux Sources

A strong answer for Flux Sources names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Solution 40: Promotion

A strong answer for Promotion names the affected GitOps source, describes the reconciliation path, separates desired and actual state and states a concrete recovery path.

Good evidence: Git commit, rendered manifest, Argo CD Application status, Flux condition, Kubernetes event or traceable diff.
Common mistake: equating GitOps with CI or enabling auto-sync without RBAC, secret and drift assessment.
Security expectation: no plaintext secrets, minimal controller permissions, checked signature or policy boundaries and documented incident response.

Practice Appendix: Intermediate Solution

This appendix provides a backlog for longer trainings, reviews and repetition. Each task is small enough to verify with local YAML artifacts and a Git repository.

A001. Kustomize

Task: document desired state and explicitly relate the observation to Kustomize.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A002. Helm

Task: identify source and commit and explicitly relate the observation to Helm.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A003. Argo CD Applications

Task: explain reconciliation path and explicitly relate the observation to Argo CD Applications.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A004. Flux Sources

Task: prove drift and explicitly relate the observation to Flux Sources.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A005. Promotion

Task: check Kustomize or Helm rendering and explicitly relate the observation to Promotion.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A006. Pull Requests

Task: read Argo CD or Flux resource and explicitly relate the observation to Pull Requests.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A007. Rollbacks

Task: assess promotion risk and explicitly relate the observation to Rollbacks.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A008. GitOps

Task: write down rollback path and explicitly relate the observation to GitOps.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A009. Desired State

Task: mark secret boundary and explicitly relate the observation to Desired State.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A010. Actual State

Task: check RBAC and tenant boundary and explicitly relate the observation to Actual State.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A011. Reconciliation

Task: name policy impact and explicitly relate the observation to Reconciliation.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A012. Drift

Task: describe feedback loop and explicitly relate the observation to Drift.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A013. Source of Truth

Task: document desired state and explicitly relate the observation to Source of Truth.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A014. Pull Model

Task: identify source and commit and explicitly relate the observation to Pull Model.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A015. Argo CD Application

Task: explain reconciliation path and explicitly relate the observation to Argo CD Application.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A016. Argo CD AppProject

Task: prove drift and explicitly relate the observation to Argo CD AppProject.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A017. Flux Source

Task: check Kustomize or Helm rendering and explicitly relate the observation to Flux Source.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A018. Flux Kustomization

Task: read Argo CD or Flux resource and explicitly relate the observation to Flux Kustomization.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A019. HelmRelease

Task: assess promotion risk and explicitly relate the observation to HelmRelease.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A020. Kustomize Overlay

Task: write down rollback path and explicitly relate the observation to Kustomize Overlay.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A021. Promotion

Task: mark secret boundary and explicitly relate the observation to Promotion.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A022. Progressive Delivery

Task: check RBAC and tenant boundary and explicitly relate the observation to Progressive Delivery.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A023. Secret Management

Task: name policy impact and explicitly relate the observation to Secret Management.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A024. Kustomize

Task: describe feedback loop and explicitly relate the observation to Kustomize.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A025. Helm

Task: document desired state and explicitly relate the observation to Helm.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A026. Argo CD Applications

Task: identify source and commit and explicitly relate the observation to Argo CD Applications.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A027. Flux Sources

Task: explain reconciliation path and explicitly relate the observation to Flux Sources.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A028. Promotion

Task: prove drift and explicitly relate the observation to Promotion.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A029. Pull Requests

Task: check Kustomize or Helm rendering and explicitly relate the observation to Pull Requests.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A030. Rollbacks

Task: read Argo CD or Flux resource and explicitly relate the observation to Rollbacks.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A031. GitOps

Task: assess promotion risk and explicitly relate the observation to GitOps.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A032. Desired State

Task: write down rollback path and explicitly relate the observation to Desired State.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A033. Actual State

Task: mark secret boundary and explicitly relate the observation to Actual State.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A034. Reconciliation

Task: check RBAC and tenant boundary and explicitly relate the observation to Reconciliation.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A035. Drift

Task: name policy impact and explicitly relate the observation to Drift.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A036. Source of Truth

Task: describe feedback loop and explicitly relate the observation to Source of Truth.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A037. Pull Model

Task: document desired state and explicitly relate the observation to Pull Model.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A038. Argo CD Application

Task: identify source and commit and explicitly relate the observation to Argo CD Application.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A039. Argo CD AppProject

Task: explain reconciliation path and explicitly relate the observation to Argo CD AppProject.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A040. Flux Source

Task: prove drift and explicitly relate the observation to Flux Source.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A041. Flux Kustomization

Task: check Kustomize or Helm rendering and explicitly relate the observation to Flux Kustomization.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A042. HelmRelease

Task: read Argo CD or Flux resource and explicitly relate the observation to HelmRelease.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A043. Kustomize Overlay

Task: assess promotion risk and explicitly relate the observation to Kustomize Overlay.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A044. Promotion

Task: write down rollback path and explicitly relate the observation to Promotion.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A045. Progressive Delivery

Task: mark secret boundary and explicitly relate the observation to Progressive Delivery.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A046. Secret Management

Task: check RBAC and tenant boundary and explicitly relate the observation to Secret Management.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A047. Kustomize

Task: name policy impact and explicitly relate the observation to Kustomize.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A048. Helm

Task: describe feedback loop and explicitly relate the observation to Helm.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A049. Argo CD Applications

Task: document desired state and explicitly relate the observation to Argo CD Applications.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A050. Flux Sources

Task: identify source and commit and explicitly relate the observation to Flux Sources.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A051. Promotion

Task: explain reconciliation path and explicitly relate the observation to Promotion.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A052. Pull Requests

Task: prove drift and explicitly relate the observation to Pull Requests.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A053. Rollbacks

Task: check Kustomize or Helm rendering and explicitly relate the observation to Rollbacks.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A054. GitOps

Task: read Argo CD or Flux resource and explicitly relate the observation to GitOps.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A055. Desired State

Task: assess promotion risk and explicitly relate the observation to Desired State.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A056. Actual State

Task: write down rollback path and explicitly relate the observation to Actual State.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A057. Reconciliation

Task: mark secret boundary and explicitly relate the observation to Reconciliation.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A058. Drift

Task: check RBAC and tenant boundary and explicitly relate the observation to Drift.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A059. Source of Truth

Task: name policy impact and explicitly relate the observation to Source of Truth.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A060. Pull Model

Task: describe feedback loop and explicitly relate the observation to Pull Model.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A061. Argo CD Application

Task: document desired state and explicitly relate the observation to Argo CD Application.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A062. Argo CD AppProject

Task: identify source and commit and explicitly relate the observation to Argo CD AppProject.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A063. Flux Source

Task: explain reconciliation path and explicitly relate the observation to Flux Source.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A064. Flux Kustomization

Task: prove drift and explicitly relate the observation to Flux Kustomization.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A065. HelmRelease

Task: check Kustomize or Helm rendering and explicitly relate the observation to HelmRelease.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A066. Kustomize Overlay

Task: read Argo CD or Flux resource and explicitly relate the observation to Kustomize Overlay.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A067. Promotion

Task: assess promotion risk and explicitly relate the observation to Promotion.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A068. Progressive Delivery

Task: write down rollback path and explicitly relate the observation to Progressive Delivery.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A069. Secret Management

Task: mark secret boundary and explicitly relate the observation to Secret Management.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A070. Kustomize

Task: check RBAC and tenant boundary and explicitly relate the observation to Kustomize.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A071. Helm

Task: name policy impact and explicitly relate the observation to Helm.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A072. Argo CD Applications

Task: describe feedback loop and explicitly relate the observation to Argo CD Applications.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A073. Flux Sources

Task: document desired state and explicitly relate the observation to Flux Sources.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

A074. Promotion

Task: identify source and commit and explicitly relate the observation to Promotion.
Evidence: Write down at least one GitOps-adjacent command, one expected result and one limit of that evidence.
Operations question: What would a wrong assumption change in dev, staging and prod clusters?
Security question: Which credentials, secrets, roles, signatures or policy rules would be critical?
Recovery: Explain whether Git revert, sync rollback, suspend, manual drift correction or secret rotation is required.

Official Sources and Scope

The material is aligned with public GitOps and Kubernetes documentation. Argo CD, Flux, Kustomize, Helm, policy controllers and secret tools are positioned where they represent common GitOps workflows. An example artifact is not an installation promise for a specific cluster.

OpenGitOps: https://opengitops.dev/
OpenGitOps Principles: https://github.com/open-gitops/documents/blob/main/PRINCIPLES.md
Argo CD Documentation: https://argo-cd.readthedocs.io/en/stable/
Argo CD Declarative Setup: https://argo-cd.readthedocs.io/en/stable/operator-manual/declarative-setup/
Argo CD Project Page: https://argoproj.github.io/cd/
Flux Documentation: https://fluxcd.io/flux/
Flux Core Concepts: https://fluxcd.io/flux/concepts/
CNCF GitOps Certified Associate (CGOA): https://www.cncf.io/training/certification/cgoa/
Linux Foundation Certified GitOps Associate (CGOA): https://training.linuxfoundation.org/certification/certified-gitops-associate-cgoa/

Additional Review Drills

Use these drills when the primary task is complete and the learner needs another pass over operational reasoning. They are intentionally evidence-oriented and can be answered with local GitOps artifacts.

Drill 01: desired state

State which source, controller or environment is affected by desired state.
Name one command or manifest field that produces evidence.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared GitOps platform.

Drill 02: source commit

State which source, controller or environment is affected by source commit.
Name one command or manifest field that produces evidence.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared GitOps platform.

Drill 03: reconciliation

State which source, controller or environment is affected by reconciliation.
Name one command or manifest field that produces evidence.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared GitOps platform.

Drill 04: drift

State which source, controller or environment is affected by drift.
Name one command or manifest field that produces evidence.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared GitOps platform.

Drill 05: Argo CD Application

State which source, controller or environment is affected by Argo CD Application.
Name one command or manifest field that produces evidence.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared GitOps platform.

Drill 06: Flux Kustomization

State which source, controller or environment is affected by Flux Kustomization.
Name one command or manifest field that produces evidence.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared GitOps platform.

Drill 07: Kustomize overlay

State which source, controller or environment is affected by Kustomize overlay.
Name one command or manifest field that produces evidence.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared GitOps platform.

Drill 08: HelmRelease

State which source, controller or environment is affected by HelmRelease.
Name one command or manifest field that produces evidence.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared GitOps platform.

Drill 09: secret management

State which source, controller or environment is affected by secret management.
Name one command or manifest field that produces evidence.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared GitOps platform.

Drill 10: RBAC boundary

State which source, controller or environment is affected by RBAC boundary.
Name one command or manifest field that produces evidence.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared GitOps platform.

Drill 11: policy gate

State which source, controller or environment is affected by policy gate.
Name one command or manifest field that produces evidence.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared GitOps platform.

Drill 12: rollback

State which source, controller or environment is affected by rollback.
Name one command or manifest field that produces evidence.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared GitOps platform.

Drill 13: desired state

State which source, controller or environment is affected by desired state.
Name one command or manifest field that produces evidence.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared GitOps platform.

Drill 14: source commit

State which source, controller or environment is affected by source commit.
Name one command or manifest field that produces evidence.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared GitOps platform.

Drill 15: reconciliation

State which source, controller or environment is affected by reconciliation.
Name one command or manifest field that produces evidence.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared GitOps platform.

Drill 16: drift

State which source, controller or environment is affected by drift.
Name one command or manifest field that produces evidence.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared GitOps platform.

GitOps Solution: Intermediate (EN)

Grading Rubric

Sample Criteria

Solution 01: Kustomize

Solution 02: Helm

Solution 03: Argo CD Applications

Solution 04: Flux Sources

Solution 05: Promotion

Solution 06: Pull Requests

Solution 07: Rollbacks

Solution 08: Kustomize

Solution 09: Helm

Solution 10: Argo CD Applications

Solution 11: Flux Sources

Solution 12: Promotion

Solution 13: Pull Requests

Solution 14: Rollbacks

Solution 15: Kustomize

Solution 16: Helm

Solution 17: Argo CD Applications

Solution 18: Flux Sources

Solution 19: Promotion

Solution 20: Pull Requests

Solution 21: Rollbacks

Solution 22: Kustomize

Solution 23: Helm

Solution 24: Argo CD Applications

Solution 25: Flux Sources

Solution 26: Promotion

Solution 27: Pull Requests

Solution 28: Rollbacks

Solution 29: Kustomize

Solution 30: Helm

Solution 31: Argo CD Applications

Solution 32: Flux Sources

Solution 33: Promotion

Solution 34: Pull Requests

Solution 35: Rollbacks

Solution 36: Kustomize

Solution 37: Helm

Solution 38: Argo CD Applications

Solution 39: Flux Sources

Solution 40: Promotion

Review Checklist for Intermediate Solution

Practice Appendix: Intermediate Solution

A001. Kustomize

A002. Helm

A003. Argo CD Applications

A004. Flux Sources

A005. Promotion

A006. Pull Requests

A007. Rollbacks

A008. GitOps

A009. Desired State

A010. Actual State

A011. Reconciliation

A012. Drift

A013. Source of Truth

A014. Pull Model

A015. Argo CD Application

A016. Argo CD AppProject

A017. Flux Source

A018. Flux Kustomization

A019. HelmRelease

A020. Kustomize Overlay

A021. Promotion

A022. Progressive Delivery

A023. Secret Management

A024. Kustomize

A025. Helm

A026. Argo CD Applications

A027. Flux Sources

A028. Promotion

A029. Pull Requests

A030. Rollbacks

A031. GitOps

A032. Desired State

A033. Actual State

A034. Reconciliation

A035. Drift