Add CI check to verify Helm chart image references are pullable#222
Merged
Add CI check to verify Helm chart image references are pullable#222
Conversation
Uses crane to verify all container image references rendered by the Helm chart exist in their registries, catching broken or deprecated registry paths (e.g. gcr.io deprecation) on every PR and weekly. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…cr.io to registry.k8s.io
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
4 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.
What was changed
Uses crane to verify all container image references rendered by the Helm chart exist in their registries, catching broken or deprecated registry paths (e.g. gcr.io deprecation) on every PR and weekly.
Why?
We missed an un-pullable image (maintainer changed the image registry) which needed to be fixed by #219 . Don't want that to happen again
Checklist
Closes
How was this tested: