ci: pull the job image through the Artifact Registry mirror - #6821
Merged
Conversation
mythical-fred
approved these changes
Aug 6, 2026
mythical-fred
left a comment
There was a problem hiding this comment.
LGTM. Mechanical swap across 13 container: blocks; push path and the macOS/Windows matrix are correctly left alone. Well-argued cost case (~70% of the Cloud NAT bill), verified on main before this PR, and the pull-through cache means no coordination window with the next feldera-dev push. Nothing to flag.
gz
enabled auto-merge
August 6, 2026 15:09
lalithsuresh
approved these changes
Aug 6, 2026
ryzhyk
approved these changes
Aug 6, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Aug 6, 2026
gz
force-pushed
the
ci/pull-images-through-ar-mirror
branch
from
August 6, 2026 19:46
9814a2c to
f93e4e5
Compare
gz
enabled auto-merge
August 6, 2026 19:46
gz
disabled auto-merge
August 6, 2026 19:47
gz
force-pushed
the
ci/pull-images-through-ar-mirror
branch
from
August 6, 2026 19:57
f93e4e5 to
9038ab2
Compare
gz
enabled auto-merge
August 6, 2026 20:44
gz
force-pushed
the
ci/pull-images-through-ar-mirror
branch
from
August 6, 2026 20:47
9038ab2 to
c2e299c
Compare
Signed-off-by: Gerd Zellweger <mail@gerdzellweger.com>
gz
force-pushed
the
ci/pull-images-through-ar-mirror
branch
from
August 7, 2026 00:09
c2e299c to
f702132
Compare
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Aug 7, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Aug 7, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Aug 7, 2026
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.
Points the
container:job image at the Artifact Registry pull-through mirror instead of ghcr.io.Why
Cloud NAT never processes traffic to Google APIs: Private Google Access always wins, so Artifact Registry pulls cost nothing in NAT data processing. Pulls from ghcr.io and docker.io are billed at $0.045/GiB
Verification
A
test-web-console-unitrun onmainafter the cluster rollout confirmed the new pod spec works: the runner image pulled fromus-central1-docker.pkg.dev/feldera-ci/ghcr-remote/actions/actions-runner, dind pulled frommirror.gcr.io/library/docker, no directghcr.io/actionspulls remained, and the job passed. CI on this PR is what exercises thefeldera-devpath.