Adds a companion guide for Lesson 3 of the GitOps Tutorial Series - #32
Draft
alexcreasy wants to merge 2 commits into
Draft
Adds a companion guide for Lesson 3 of the GitOps Tutorial Series#32alexcreasy wants to merge 2 commits into
alexcreasy wants to merge 2 commits into
Conversation
Signed-off-by: Alex Creasy <alex@creasy.dev>
Signed-off-by: Alex Creasy <alex@creasy.dev>
tomncooper
reviewed
Aug 13, 2026
tomncooper
left a comment
tomncooper
left a comment
Member
There was a problem hiding this comment.
LGTM, just a couple of suggestions.
| Yet underneath, the system is broken. | ||
| The configuration you pushed describes something the underlying platform cannot actually do. | ||
| This is not a hypothetical edge case. | ||
| It is a failure mode that every team running operator-managed infrastructure will encounter sooner or later. |
Member
There was a problem hiding this comment.
Suggested change
| It is a failure mode that every team running operator-managed infrastructure will encounter sooner or later. | |
| It is a failure mode that every team running production infrastructure will encounter sooner or later. | |
| Often, you will set-up tests in you CI system to check the configurations for common errors before they are pushed to the CD system. | |
| However, you can't test for everything and sometime issues can slip through, valid changes can be made in error or people can simply change their mind. |
| It is a failure mode that every team running operator-managed infrastructure will encounter sooner or later. | ||
|
|
||
| This lesson tackles that scenario head-on. | ||
| You will learn how to distinguish between a successful sync and a genuinely healthy deployment, and when things go wrong, how to roll back safely using Git alone. |
Member
There was a problem hiding this comment.
Suggested change
| You will learn how to distinguish between a successful sync and a genuinely healthy deployment, and when things go wrong, how to roll back safely using Git alone. | |
| You will learn how to distinguish between a successful sync and a genuinely healthy deployment, and when things go wrong, how to roll back safely with a single commit. |
| ## Sync Status vs Health Status | ||
|
|
||
| ArgoCD tracks two independent statuses for every Application it manages. | ||
| *Sync status* tells you whether ArgoCD successfully applied the manifests from your Git repository to Kubernetes. |
Member
There was a problem hiding this comment.
Are we calling them "manifests" or "configurations". Are configurations upstream of manifests? Is it config > kustomize > manifests?
I am not saying that is wrong, just want to make sure we are being consistent.
|
|
||
| Consider a configuration change that the Kubernetes API accepts but the platform rejects. | ||
| The Custom Resource is stored, so ArgoCD reports `Synced`. | ||
| But the operator that manages that resource inspects the change, determines it violates a platform-level constraint, and marks the resource as not ready. |
Member
There was a problem hiding this comment.
Suggested change
| But the operator that manages that resource inspects the change, determines it violates a platform-level constraint, and marks the resource as not ready. | |
| But the operator that manages that resource inspects the change, determines it violates a constraint of the system it manages, and marks the resource as not ready. |
|
|
||
| There are two ways to undo a commit in Git, and they have very different implications in a GitOps context. | ||
|
|
||
| `git revert` creates a new commit that applies the exact inverse of the target commit. |
Member
There was a problem hiding this comment.
Suggested change
| `git revert` creates a new commit that applies the exact inverse of the target commit. | |
| `git revert <commit hash>` creates a new commit that applies the exact inverse of the target commit. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is an initial draft, as with the other lessons I'll add in hyperlinks and some instructions for checking out the repository before converting to a full PR.
Closes #24