Rules

• Do not use production secrets.
• Justify every answer with GitOps terminology.
• Separate source, desired state, actual state, controller and feedback.
• Name recovery steps when you mention risky syncs or secret cases.

Questions

Question 01: Kustomize

Describe a realistic GitOps scenario for Kustomize. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 02: Helm

Describe a realistic GitOps scenario for Helm. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 03: Argo CD Applications

Describe a realistic GitOps scenario for Argo CD Applications. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 04: Flux Sources

Describe a realistic GitOps scenario for Flux Sources. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 05: Promotion

Describe a realistic GitOps scenario for Promotion. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 06: Pull Requests

Describe a realistic GitOps scenario for Pull Requests. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 07: Rollbacks

Describe a realistic GitOps scenario for Rollbacks. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 08: Kustomize

Describe a realistic GitOps scenario for Kustomize. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 09: Helm

Describe a realistic GitOps scenario for Helm. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 10: Argo CD Applications

Describe a realistic GitOps scenario for Argo CD Applications. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 11: Flux Sources

Describe a realistic GitOps scenario for Flux Sources. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 12: Promotion

Describe a realistic GitOps scenario for Promotion. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 13: Pull Requests

Describe a realistic GitOps scenario for Pull Requests. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 14: Rollbacks

Describe a realistic GitOps scenario for Rollbacks. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 15: Kustomize

Describe a realistic GitOps scenario for Kustomize. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 16: Helm

Describe a realistic GitOps scenario for Helm. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 17: Argo CD Applications

Describe a realistic GitOps scenario for Argo CD Applications. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 18: Flux Sources

Describe a realistic GitOps scenario for Flux Sources. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 19: Promotion

Describe a realistic GitOps scenario for Promotion. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 20: Pull Requests

Describe a realistic GitOps scenario for Pull Requests. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 21: Rollbacks

Describe a realistic GitOps scenario for Rollbacks. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 22: Kustomize

Describe a realistic GitOps scenario for Kustomize. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 23: Helm

Describe a realistic GitOps scenario for Helm. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 24: Argo CD Applications

Describe a realistic GitOps scenario for Argo CD Applications. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 25: Flux Sources

Describe a realistic GitOps scenario for Flux Sources. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 26: Promotion

Describe a realistic GitOps scenario for Promotion. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 27: Pull Requests

Describe a realistic GitOps scenario for Pull Requests. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 28: Rollbacks

Describe a realistic GitOps scenario for Rollbacks. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 29: Kustomize

Describe a realistic GitOps scenario for Kustomize. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 30: Helm

Describe a realistic GitOps scenario for Helm. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 31: Argo CD Applications

Describe a realistic GitOps scenario for Argo CD Applications. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 32: Flux Sources

Describe a realistic GitOps scenario for Flux Sources. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 33: Promotion

Describe a realistic GitOps scenario for Promotion. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 34: Pull Requests

Describe a realistic GitOps scenario for Pull Requests. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 35: Rollbacks

Describe a realistic GitOps scenario for Rollbacks. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 36: Kustomize

Describe a realistic GitOps scenario for Kustomize. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 37: Helm

Describe a realistic GitOps scenario for Helm. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 38: Argo CD Applications

Describe a realistic GitOps scenario for Argo CD Applications. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 39: Flux Sources

Describe a realistic GitOps scenario for Flux Sources. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Question 40: Promotion

Describe a realistic GitOps scenario for Promotion. Which source is affected, which controller reconciles, what drift or security risk appears and which recovery path is appropriate?

Practical Case Study

You inherit a platform with Argo CD, Flux, multiple clusters, unclear repository structure and possible plaintext secrets. Build a review plan covering sources, controllers, RBAC, AppProjects, Flux Kustomizations, promotion, drift, secrets and observability.

Review Checklist for Intermediate Assessment

• 01. document desired state: record which source, commit, resource, controller and status are affected.
• 02. identify source and commit: record which source, commit, resource, controller and status are affected.
• 03. explain reconciliation path: record which source, commit, resource, controller and status are affected.
• 04. prove drift: record which source, commit, resource, controller and status are affected.
• 05. check Kustomize or Helm rendering: record which source, commit, resource, controller and status are affected.
• 06. read Argo CD or Flux resource: record which source, commit, resource, controller and status are affected.
• 07. assess promotion risk: record which source, commit, resource, controller and status are affected.
• 08. write down rollback path: record which source, commit, resource, controller and status are affected.
• 09. mark secret boundary: record which source, commit, resource, controller and status are affected.
• 10. check RBAC and tenant boundary: record which source, commit, resource, controller and status are affected.
• 11. name policy impact: record which source, commit, resource, controller and status are affected.
• 12. describe feedback loop: record which source, commit, resource, controller and status are affected.
• 13. document desired state: record which source, commit, resource, controller and status are affected.
• 14. identify source and commit: record which source, commit, resource, controller and status are affected.
• 15. explain reconciliation path: record which source, commit, resource, controller and status are affected.
• 16. prove drift: record which source, commit, resource, controller and status are affected.
• 17. check Kustomize or Helm rendering: record which source, commit, resource, controller and status are affected.
• 18. read Argo CD or Flux resource: record which source, commit, resource, controller and status are affected.
• 19. assess promotion risk: record which source, commit, resource, controller and status are affected.
• 20. write down rollback path: record which source, commit, resource, controller and status are affected.
• 21. mark secret boundary: record which source, commit, resource, controller and status are affected.
• 22. check RBAC and tenant boundary: record which source, commit, resource, controller and status are affected.
• 23. name policy impact: record which source, commit, resource, controller and status are affected.
• 24. describe feedback loop: record which source, commit, resource, controller and status are affected.
• 25. document desired state: record which source, commit, resource, controller and status are affected.
• 26. identify source and commit: record which source, commit, resource, controller and status are affected.
• 27. explain reconciliation path: record which source, commit, resource, controller and status are affected.
• 28. prove drift: record which source, commit, resource, controller and status are affected.
• 29. check Kustomize or Helm rendering: record which source, commit, resource, controller and status are affected.
• 30. read Argo CD or Flux resource: record which source, commit, resource, controller and status are affected.
• 31. assess promotion risk: record which source, commit, resource, controller and status are affected.
• 32. write down rollback path: record which source, commit, resource, controller and status are affected.
• 33. mark secret boundary: record which source, commit, resource, controller and status are affected.
• 34. check RBAC and tenant boundary: record which source, commit, resource, controller and status are affected.
• 35. name policy impact: record which source, commit, resource, controller and status are affected.
• 36. describe feedback loop: record which source, commit, resource, controller and status are affected.

Practice Appendix: Intermediate Assessment

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.

A075. Pull Requests

• Task: explain reconciliation path 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.

A076. Rollbacks

• Task: prove drift 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.

A077. GitOps

• Task: check Kustomize or Helm rendering 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.

A078. Desired State

• Task: read Argo CD or Flux resource 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.

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.