Orthevs Orthevs Fathom new horizons
Menu

Workshop wiki · English

Progressive Delivery Rollout (EN)

This detail document describes example 25-progressive-delivery-rollout. Focus: Rollout-Strategie, Analyse und kontrollierte Auslieferung.

Content language · EnglishSize · 44.2 KBexamples/25-progressive-delivery-rollout/docs/en/README.md
Workshop examples as ZIP files
Learning progress in the web app

Mark chapters as read, view reading progress and check off practice modules after enabling the optional web app. Workshop progress is calculated from chapters across all document pages. Your choices stay on this device; there is no account or server sync. Installation is not required. Withdrawing your choice in Privacy settings deletes the progress.

Reading progress0%
0%
0 / 7 chapters read
Other language versionGerman ↗Greek ↗

Progressive Delivery Rollout (EN)

This detail document describes example 25-progressive-delivery-rollout. Focus: Rollout-Strategie, Analyse und kontrollierte Auslieferung.

Learning Goals

  • Name GitOps states before changing anything.
  • Separate source, commit, rendering and target namespace.
  • Distinguish local validation from real controller execution.
  • Store evidence in a traceable way.
  • Document drift, rollback and security boundaries.
01 / 07

Flow

  1. Open the files in the example directory.
  2. Read commands.sh before executing commands blindly.
  3. Run ./run.sh and inspect work/evidence/.
  4. Compare log-graph.txt, promotion-diff.txt, status.txt and static validation results.
  5. Explain what Argo CD or Flux would additionally observe in a real cluster.
02 / 07

Expected Observations

  • Observation 01: Check Rollout-Strategie, Analyse und kontrollierte Auslieferung and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 02: Check Desired state and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 03: Check Source commit and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 04: Check Rendering and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 05: Check Controller and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 06: Check Drift and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 07: Check Secret boundary and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 08: Check Rollback and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 09: Check Rollout-Strategie, Analyse und kontrollierte Auslieferung and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 10: Check Desired state and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 11: Check Source commit and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 12: Check Rendering and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 13: Check Controller and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 14: Check Drift and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 15: Check Secret boundary and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 16: Check Rollback and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 17: Check Rollout-Strategie, Analyse und kontrollierte Auslieferung and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 18: Check Desired state and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 19: Check Source commit and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 20: Check Rendering and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 21: Check Controller and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 22: Check Drift and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 23: Check Secret boundary and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 24: Check Rollback and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 25: Check Rollout-Strategie, Analyse und kontrollierte Auslieferung and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 26: Check Desired state and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 27: Check Source commit and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 28: Check Rendering and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 29: Check Controller and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 30: Check Drift and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 31: Check Secret boundary and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 32: Check Rollback and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 33: Check Rollout-Strategie, Analyse und kontrollierte Auslieferung and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 34: Check Desired state and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 35: Check Source commit and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 36: Check Rendering and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 37: Check Controller and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 38: Check Drift and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 39: Check Secret boundary and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 40: Check Rollback and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 41: Check Rollout-Strategie, Analyse und kontrollierte Auslieferung and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 42: Check Desired state and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 43: Check Source commit and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 44: Check Rendering and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 45: Check Controller and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 46: Check Drift and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 47: Check Secret boundary and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 48: Check Rollback and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 49: Check Rollout-Strategie, Analyse und kontrollierte Auslieferung and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 50: Check Desired state and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 51: Check Source commit and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 52: Check Rendering and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 53: Check Controller and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 54: Check Drift and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 55: Check Secret boundary and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 56: Check Rollback and record which GitOps-adjacent evidence makes the observation reliable.
  • Observation 57: Check Rollout-Strategie, Analyse und kontrollierte Auslieferung and record which GitOps-adjacent evidence makes the observation reliable.
03 / 07

Review Checklist for Example Progressive Delivery Rollout

  • 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.
04 / 07

Practice Appendix: Example Progressive Delivery Rollout

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. Rollout-Strategie, Analyse und kontrollierte Auslieferung

  • Task: document desired state and explicitly relate the observation to Rollout-Strategie, Analyse und kontrollierte Auslieferung.
  • 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. OpenGitOps

  • Task: identify source and commit and explicitly relate the observation to OpenGitOps.
  • 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

  • Task: explain reconciliation path and explicitly relate the observation to Argo CD.
  • 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

  • Task: prove drift and explicitly relate the observation to Flux.
  • 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. Kustomize

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

A006. Helm

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

A007. Policy

  • Task: assess promotion risk and explicitly relate the observation to Policy.
  • 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. Secrets

  • Task: write down rollback path and explicitly relate the observation to Secrets.
  • 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. Rollout-Strategie, Analyse und kontrollierte Auslieferung

  • Task: mark secret boundary and explicitly relate the observation to Rollout-Strategie, Analyse und kontrollierte Auslieferung.
  • 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. OpenGitOps

  • Task: check RBAC and tenant boundary and explicitly relate the observation to OpenGitOps.
  • 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. Argo CD

  • Task: name policy impact and explicitly relate the observation to Argo CD.
  • 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. Flux

  • Task: describe feedback loop and explicitly relate the observation to Flux.
  • 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. 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.

A014. 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.

A015. Policy

  • Task: explain reconciliation path and explicitly relate the observation to Policy.
  • 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. Secrets

  • Task: prove drift and explicitly relate the observation to Secrets.
  • 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. Rollout-Strategie, Analyse und kontrollierte Auslieferung

  • Task: check Kustomize or Helm rendering and explicitly relate the observation to Rollout-Strategie, Analyse und kontrollierte Auslieferung.
  • 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. OpenGitOps

  • Task: read Argo CD or Flux resource and explicitly relate the observation to OpenGitOps.
  • 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. Argo CD

  • Task: assess promotion risk and explicitly relate the observation to Argo CD.
  • 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. Flux

  • Task: write down rollback path and explicitly relate the observation to Flux.
  • 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. Kustomize

  • Task: mark secret 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.

A022. Helm

  • Task: check RBAC and tenant boundary 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.

A023. Policy

  • Task: name policy impact and explicitly relate the observation to Policy.
  • 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. Secrets

  • Task: describe feedback loop and explicitly relate the observation to Secrets.
  • 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. Rollout-Strategie, Analyse und kontrollierte Auslieferung

  • Task: document desired state and explicitly relate the observation to Rollout-Strategie, Analyse und kontrollierte Auslieferung.
  • 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. OpenGitOps

  • Task: identify source and commit and explicitly relate the observation to OpenGitOps.
  • 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. Argo CD

  • Task: explain reconciliation path and explicitly relate the observation to Argo CD.
  • 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. Flux

  • Task: prove drift and explicitly relate the observation to Flux.
  • 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. Kustomize

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

A030. Helm

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

A031. Policy

  • Task: assess promotion risk and explicitly relate the observation to Policy.
  • 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. Secrets

  • Task: write down rollback path and explicitly relate the observation to Secrets.
  • 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. Rollout-Strategie, Analyse und kontrollierte Auslieferung

  • Task: mark secret boundary and explicitly relate the observation to Rollout-Strategie, Analyse und kontrollierte Auslieferung.
  • 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. OpenGitOps

  • Task: check RBAC and tenant boundary and explicitly relate the observation to OpenGitOps.
  • 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. Argo CD

  • Task: name policy impact and explicitly relate the observation to Argo CD.
  • 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. Flux

  • Task: describe feedback loop and explicitly relate the observation to Flux.
  • 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. 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.

A038. 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.

A039. Policy

  • Task: explain reconciliation path and explicitly relate the observation to Policy.
  • 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. Secrets

  • Task: prove drift and explicitly relate the observation to Secrets.
  • 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. Rollout-Strategie, Analyse und kontrollierte Auslieferung

  • Task: check Kustomize or Helm rendering and explicitly relate the observation to Rollout-Strategie, Analyse und kontrollierte Auslieferung.
  • 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. OpenGitOps

  • Task: read Argo CD or Flux resource and explicitly relate the observation to OpenGitOps.
  • 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. Argo CD

  • Task: assess promotion risk and explicitly relate the observation to Argo CD.
  • 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. Flux

  • Task: write down rollback path and explicitly relate the observation to Flux.
  • 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. Kustomize

  • Task: mark secret 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.

A046. Helm

  • Task: check RBAC and tenant boundary 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.

A047. Policy

  • Task: name policy impact and explicitly relate the observation to Policy.
  • 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. Secrets

  • Task: describe feedback loop and explicitly relate the observation to Secrets.
  • 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.
05 / 07

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/
06 / 07

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.
07 / 07

GOP · Orthevs Academy

31 modules as one continuous learning path.

The sequence remains unchanged: from the lab skeleton through technical foundations and operating models to final troubleshooting. The technical directory names are deliberately preserved.

Practice modules

Orthevs as an app

Install Orthevs

The Orthevs web app can be installed on supported mobile devices and desktop browsers.

iPhone and iPad

Open Orthevs in Safari. Tap Share, then Add to Home Screen. Enable Open as Web App if offered, then tap Add.

Android

For the web app, open the browser menu and choose Install app or Add to Home screen. Confirm the installation.

Desktop browser

Open the browser menu or the install icon in the address bar, then choose Install app or Add to Dock.

Web app installation depends on your browser. If no install prompt appears, follow the browser steps shown above.