[Kafka] Fix KafkaToPubsubE2ETest by bumping the purged cloud-sdk emulator image tag - #39956
Merged
Merged
Conversation
gcr.io purged the 316.0.0 tag family, so the pinned cloud-sdk:316.0.0-emulators image 404s and the PubSub emulator container fails in the class rule, breaking every Java PreCommit run since 2026-09-01. Pin the newest versioned emulator tag instead. Verified locally, the container starts and the E2E test passes.
tkaymak
changed the title
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.
Fixes #39955.
gcr.io purged the 316.0.0 tag family from cloudsdktool/cloud-sdk, the registry returns 404 manifest unknown and the tags list has no 316.0.0 entries left.
KafkaToPubsubE2ETest pins that tag for its PubSub emulator container, so the class rule fails before any test runs and every beam_PreCommit_Java run has been red since 2026-09-01 roughly 02:30 UTC, on master (runs 33488230103 and 33478152767) and on every PR.
This bumps the pin to 583.0.0-emulators, the newest versioned emulator tag. Verified locally with Docker, the container pulls and starts on the new image and testKafkaToPubsubE2E passes.
If preferred we can use the rolling emulators tag, at the cost of a moving image.
Happy to switch 👯
R: @Abacn