chore(deps): opencost, reloader and trivy-operator to current - #192
Merged
Conversation
Three chart bumps whose rendered output does not change beyond the version strings themselves. opencost 2.5.28 -> 2.5.29 reloader 2.2.14 -> 2.2.15 (appVersion v1.4.19 -> v1.4.20) trivy-operator 0.34.0 -> 0.35.0 (appVersion 0.32.0 -> 0.33.0) Batched together because they are the low-blast-radius end of the current currency gap. The three that are not here are deliberately not here: cilium crosses a CNI minor and takes its own change, the otel collector bump needs its image pin resolved in the same commit or it opens a chart-ahead-of-image divergence, and external-secrets 2.9.0 published today and sits inside the shared preset's three-day minimumReleaseAge. Verified by rendering rather than by reading the version numbers. Each chart was templated at both versions against this repo's own base plus production values and the outputs diffed: no object added, removed or renamed in any of the three, and every changed line is a version string, an image tag, a chart label, or — for trivy-operator — the config checksum that follows from them. trivy-operator's appVersion moves a minor and it ships CRDs, which `helm template` does not render and the render gate therefore cannot see. Both versions were pulled and their crds/ directories compared directly: twelve files each, byte-identical. This matters because ArgoCD syncs these with ServerSideApply and no skipCrds, so a CRD change here applies fleet-wide without passing through any gate in this repo. task validate passes: 109 addon×env combinations, 0 failed.
CI Results
All checks passed. |
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
1 participant
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
What is deliberately not here
minimumReleaseAge.How it was verified
Not by reading version numbers. Each chart was templated at both versions against this repo's own base + production values and the outputs diffed:
The CRD gap, closed explicitly. trivy-operator moves an appVersion minor and ships CRDs — which
helm templatedoes not render, sohelm-renderstructurally cannot see them. Both versions were pulled and theircrds/directories compared directly: twelve files each, byte-identical. This matters because ArgoCD syncs withServerSideApplyand noskipCrds, so a CRD change here reaches the fleet without passing any gate in this repo.task validatepasses — 109 addon×env combinations, 0 failed.kx mirrors all three and follows in a paired PR once this lands, since
mirror-checkcompares against this repo at a pinned ref.