mirror kafka-exporter master build by digest - #43
Closed
yaroslavmokflmg wants to merge 1 commit into
Closed
Conversation
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.
danielqsj/kafka_exporter has had no tagged release since v1.9.0 (2025-02-17), and master has not moved since 2026-04-13. The Go and golang.org/x/crypto CVE fixes - including CVE-2025-22871, the only CRITICAL with a public exploit in the detected set - exist only on master, published as :latest.
:latest was built 2026-04-13, fourteen months after v1.9.0, so it carries those fixes. This mirrors it by digest rather than by tag, into an immutable local tag, so the deployed reference cannot drift when upstream moves :latest - the same failure mode that already left the NATS fleet running two versions behind one floating tag.
The existing repository rule stays: its allow regex ('v[0-9]+.[0-9]+.[0-9]+') can never pick an untagged digest up, which is why a separate entry is needed.
Nothing is deployed by this PR. After merge the sync has to be run by hand via workflow_dispatch - the schedule is weekly, Sundays 02:00 UTC. The manifests in openframe-saas-shared (datasources/kafka and datasources/kafka-tenant, where the registry key is currently commented out so the pull falls through to docker.io) switch over in a follow-up PR, only once the tag is confirmed present on the mirror.
Ref: docs/soc2/scc/t6-kafka-exporter-no-upstream-fix.md