DevOps Practitioner · Module 8: GitOps and incident response · Lab
Diagnose Manual-Change versus Desired-State Conflict
45 min hands-on · Core
The L46 setup with a demo app under GitOps supervision; one staged manual change with a scenario brief (hotfix or accident).
Local guide: run the steps below on your own machine in order, then check the validation list.
Objectives
- Read the sync diff and classify the drift
- Adopt a correct hotfix into git or revert an accident
- Record the decision with its reason and the guard added
Step 1
Read the conflict
Stage the provided manual change (a scale-up with a traffic-spike brief). Read the sync diff and classify: hotfix, experiment or accident, with the reason written down.
Step 2
Resolve by branch
Adopt the hotfix into git with the incident reference and watch the agent confirm, or revert the accident and record the guard (preview requirement, narrower access).
Step 3
Show the precedent
Write the one-paragraph precedent: how the next same-shaped drift resolves without an argument. Quote the final converged state.
How to confirm it worked
- Sync diff quoted with a written classification
- Adopt or revert executed with the reason recorded
- Guard or reference present for the branch taken
- Precedent paragraph written