By the end
What you'll build
- State the GitOps principles and explain what each one rules out in practice
- Design a repository layout for multiple environments and teams with clear review boundaries
- Promote configuration between environments without duplicating or diverging definitions
- Diagnose a reconciliation loop that will not converge, including drift, pruning and health assessment
- Keep secrets out of version control while preserving a pull-based reconciliation model
- Roll back a change and reconstruct an audit trail from version history
Curriculum
What's inside
7 modules · 35 lessons
- 01
Principles
5 lessons- The GitOps principles and what each one rules out
- Declarative desired state
- Version control as the single source of truth
- Pull-based reconciliation compared with pushed deployment
- What each commitment rules outmatch pairs
- 02
Repository design
5 lessons- Structuring repositories for many environments and many teams
- Single-repository and multi-repository trade-offs
- Separating application code from delivery configuration
- Ownership and code review boundaries
- Complete the layout rulesfill blank
- 03
Configuration management
5 lessons- Templating and overlays without losing readability
- Environment promotion by configuration change
- Managing shared defaults across teams
- Rendering and validating manifests before merge
- Promote a release without rebuilding itsequence order
- 04
Reconciliation in practice
5 lessons- Reading a reconciliation loop when it will not converge
- Drift, self-healing and pruning
- Health assessment and ordered synchronisation
- Resources the loop must be told not to touch
- The loop that will not convergescenario
- 05
Secrets and sensitive configuration
5 lessons- Keeping secrets out of the repository while keeping GitOps
- Encrypted-at-rest patterns
- External secret references
- Rotation and revocation without breaking reconciliation
- What each secret decision costs youmatch pairs
- 06
Operating at scale
5 lessons- Progressive delivery and rollback with a pull-based model
- Multi-cluster and multi-tenant repository layouts
- Change auditing and the evidence trail
- Incident response when the repository is the control surface
- Releasing, reverting and proving itfill blank
- 07
Practice and check
5 lessons- What the loop is telling youmatch pairs
- Undoing a bad release in a pull-based systemsequence order
- Saying it preciselyfill blank
- A crash loop at the weekendscenario
- Course quizquiz
The shape of it
How this course works
Short lessons
35 lessons across 7 modules, each small enough to finish in one sitting.
Practice as you go
Every lesson ends with a small space for what you noticed — the doing is the learning.
Progress you can see
Your progress is saved lesson by lesson, ready whenever you come back.
Ready when you are.
Make an account and this course opens up — your progress is saved from the very first lesson.
