GitOps operations knowledge check and Gate 4¶
Operations quiz¶
- How does drift differ from an invalid desired state?
- Why should diagnosis proceed from sources toward workloads?
- What remains running when an
OCIRepositorytag becomes unavailable? - Which evidence distinguishes an OCI authentication failure from a Helm hook failure?
- Why can a manual
helm rollbackbe temporary under Flux? - What does suspending a
HelmReleasechange, and what does it not change? - When is explicit reconciliation preferable to waiting for the interval?
- Compare credential exposure in GitLab CI push and Flux pull delivery.
Final synthesis quiz¶
- Trace a values commit to a Pod update through every Flux resource.
- Explain Helm values precedence with a dependency example.
- Explain why Workload Identity is preferred to a JSON key.
- Assign five likely failures to their owning controllers.
- Describe a safe rollback for a bad chart version.
- Explain what each readiness gate proved that the previous gate did not.
Gate 4 live demonstration¶
Ask a peer to choose, without telling you in advance:
- replica drift;
- a nonexistent OCI tag;
- a failed Helm hook;
- suspended reconciliation.
You must:
- identify the scenario using status, conditions, events, and logs;
- name the owning controller;
- recover through Git when desired state is wrong;
- prove all Flux resources and the workload are Ready;
- defend your Flux-versus-CI comparison under follow-up questions.
Pass: correct diagnosis before remediation, durable recovery, and a complete explanation of control and credentials.
After passing, use the cleanup guide or continue with image automation, environment overlays, or progressive delivery as a separate track.