Clarify how Helm chart updates track image updates#3615
Merged
Conversation
…dates-track-image-updates Signed-off-by: Mark Drake <mark@chainguard.dev>
✅ Deploy Preview for ornate-narwhal-088216 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
joshrwolf
reviewed
Jul 20, 2026
…igests pin Signed-off-by: Mark Drake <mark@chainguard.dev>
joshrwolf
reviewed
Jul 20, 2026
joshrwolf
reviewed
Jul 20, 2026
joshrwolf
reviewed
Jul 20, 2026
Signed-off-by: Mark Drake <mark@chainguard.dev>
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
3 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.
[ ] Check if this is a typo or other quick fix and ignore the rest :)
Type of change
Documentation Update
What should this PR do?
resolves https://linear.app/chainguard/issue/DOCS-72/clarify-how-helm-chart-updates-track-image-updates
Clarifies how image updates propagate to customers depending on whether they reference a Chainguard Helm chart by tag or by digest.
Why are we making this change?
Customers were unclear on what happens to the underlying images when Chainguard updates them. Referencing a chart by tag keeps deployments current with the latest image digests automatically, while pinning by digest requires updating the pin to receive newer images — a distinction the guide did not spell out.
What are the acceptance criteria?
How should this PR be tested?
Any documentation published to Chainguard Academy is reviewed carefully for accuracy. GUI procedures, API commands, and CLI code snippets in a draft are run and tested thoroughly — by both the author and the reviewer — to confirm they work exactly as written. This helps ensure that readers can follow along and get the same results. See the `edu` repo's README.