cloudbuild: bump gcb-docker-gcloud to v20260205-38cfa9523f#1399
Merged
k8s-ci-robot merged 1 commit intoMay 5, 2026
Conversation
The cloud-provider-aws-push-images postsubmit has been failing across all branches (master and release-*) since early April 2026 because cloudbuild.yaml pins gcr.io/k8s-staging-test-infra/gcb-docker-gcloud:v20221214-1b4dd4d69a, and that tag has been garbage-collected out of the staging registry. Cloud Build retries the pull 10 times and fails with 'manifest unknown: Failed to fetch "v20221214-1b4dd4d69a"'. Example failed run (v1.36.0 tag): https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/cloud-provider-aws-push-images/2051449456091467776 Bumping to v20260205-38cfa9523f (digest sha256:ff388e0dc16351e96f8464e2e185b74a7578a5ccb7a112cf3393468e59e6e2d2), currently the newest tag in gcr.io/k8s-staging-test-infra/gcb-docker-gcloud and aliased to 'latest'. This image still provides /buildx-entrypoint used by the build step. Signed-off-by: Ganesh Putta <ganiredi@amazon.com>
k8s-ci-robot
added
the
do-not-merge/release-note-label-needed
k8s-ci-robot
added
needs-kind
Contributor
|
This issue is currently awaiting triage. If cloud-provider-aws contributors determine this is a relevant issue, they will accept it by applying the The DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
k8s-ci-robot
added
the
needs-ok-to-test
Contributor
|
Hi @Ganiredi. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Tip We noticed you've done this a few times! Consider joining the org to skip this step and gain Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
k8s-ci-robot
added
size/XS
Member
|
/ok-to-test |
k8s-ci-robot
added
ok-to-test
Member
|
/release-note-none |
k8s-ci-robot
added
release-note-none
Contributor
Author
|
/retest |
Member
|
/lgtm |
k8s-ci-robot
added
the
lgtm
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kmala The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
approved
This was referenced May 5, 2026
Merged
Closed
Closed
Closed
This was referenced May 5, 2026
Closed
Closed
k8s-ci-robot
added a commit
that referenced
this pull request
May 5, 2026
…-upstream-release-1.36 Automated cherry pick of #1399: cloudbuild: bump gcb-docker-gcloud to v20260205-38cfa9523f
k8s-ci-robot
pushed a commit
that referenced
this pull request
May 5, 2026
The cloud-provider-aws-push-images postsubmit has been running up against the 1200s (20 min) Cloud Build timeout: - The new gcb-docker-gcloud image (pinned in #1399) is larger and pushes/pulls take slightly longer, and GCB's shared pool has been slower overall, so step 1 (multi-arch buildx) routinely now uses 16-19 of the 20 available minutes. - Step 2 (cloudbuild-artifacts) then has almost no budget left and is killed mid-`hack/install-gsutil.sh`, which means the ecr-credential-provider binaries never reach gs://k8s-staging-provider-aws/releases/. Observed failures after #1399 landed: - release-1.36: https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/cloud-provider-aws-push-images/2051718180123971584 (step 1 ok, step 2 TIMEOUT installing gsutil) - master: https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/cloud-provider-aws-push-images/2051514822092132352 (step 1 buildkit session deadline during registry push) Cross-check: the last successful binary upload to the staging releases bucket was v1.35.1-5-g7dac1f6 on 2026-03-27 — step 2 has effectively been timing out for over a month, independent of the image pin issue. Bumping the overall build timeout to 3600s (60 min) gives headroom for GCB variability, keeps step 1 multi-arch pushes reliable, and leaves enough budget for the existing install-gsutil + upload flow. A follow-up PR can skip the SDK reinstall by switching the step 2 base image. Signed-off-by: Ganesh Putta <ganiredi@amazon.com>
k8s-ci-robot
pushed a commit
that referenced
this pull request
May 6, 2026
The cloud-provider-aws-push-images postsubmit has been running up against the 1200s (20 min) Cloud Build timeout: - The new gcb-docker-gcloud image (pinned in #1399) is larger and pushes/pulls take slightly longer, and GCB's shared pool has been slower overall, so step 1 (multi-arch buildx) routinely now uses 16-19 of the 20 available minutes. - Step 2 (cloudbuild-artifacts) then has almost no budget left and is killed mid-`hack/install-gsutil.sh`, which means the ecr-credential-provider binaries never reach gs://k8s-staging-provider-aws/releases/. Observed failures after #1399 landed: - release-1.36: https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/cloud-provider-aws-push-images/2051718180123971584 (step 1 ok, step 2 TIMEOUT installing gsutil) - master: https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/cloud-provider-aws-push-images/2051514822092132352 (step 1 buildkit session deadline during registry push) Cross-check: the last successful binary upload to the staging releases bucket was v1.35.1-5-g7dac1f6 on 2026-03-27 — step 2 has effectively been timing out for over a month, independent of the image pin issue. Bumping the overall build timeout to 3600s (60 min) gives headroom for GCB variability, keeps step 1 multi-arch pushes reliable, and leaves enough budget for the existing install-gsutil + upload flow. A follow-up PR can skip the SDK reinstall by switching the step 2 base image. Signed-off-by: Ganesh Putta <ganiredi@amazon.com>
This was referenced May 6, 2026
k8s-ci-robot
pushed a commit
that referenced
this pull request
May 7, 2026
The cloud-provider-aws-push-images postsubmit has been running up against the 1200s (20 min) Cloud Build timeout: - The new gcb-docker-gcloud image (pinned in #1399) is larger and pushes/pulls take slightly longer, and GCB's shared pool has been slower overall, so step 1 (multi-arch buildx) routinely now uses 16-19 of the 20 available minutes. - Step 2 (cloudbuild-artifacts) then has almost no budget left and is killed mid-`hack/install-gsutil.sh`, which means the ecr-credential-provider binaries never reach gs://k8s-staging-provider-aws/releases/. Observed failures after #1399 landed: - release-1.36: https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/cloud-provider-aws-push-images/2051718180123971584 (step 1 ok, step 2 TIMEOUT installing gsutil) - master: https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/cloud-provider-aws-push-images/2051514822092132352 (step 1 buildkit session deadline during registry push) Cross-check: the last successful binary upload to the staging releases bucket was v1.35.1-5-g7dac1f6 on 2026-03-27 — step 2 has effectively been timing out for over a month, independent of the image pin issue. Bumping the overall build timeout to 3600s (60 min) gives headroom for GCB variability, keeps step 1 multi-arch pushes reliable, and leaves enough budget for the existing install-gsutil + upload flow. A follow-up PR can skip the SDK reinstall by switching the step 2 base image. Signed-off-by: Ganesh Putta <ganiredi@amazon.com>
k8s-ci-robot
pushed a commit
that referenced
this pull request
May 7, 2026
The cloud-provider-aws-push-images postsubmit has been running up against the 1200s (20 min) Cloud Build timeout: - The new gcb-docker-gcloud image (pinned in #1399) is larger and pushes/pulls take slightly longer, and GCB's shared pool has been slower overall, so step 1 (multi-arch buildx) routinely now uses 16-19 of the 20 available minutes. - Step 2 (cloudbuild-artifacts) then has almost no budget left and is killed mid-`hack/install-gsutil.sh`, which means the ecr-credential-provider binaries never reach gs://k8s-staging-provider-aws/releases/. Observed failures after #1399 landed: - release-1.36: https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/cloud-provider-aws-push-images/2051718180123971584 (step 1 ok, step 2 TIMEOUT installing gsutil) - master: https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/cloud-provider-aws-push-images/2051514822092132352 (step 1 buildkit session deadline during registry push) Cross-check: the last successful binary upload to the staging releases bucket was v1.35.1-5-g7dac1f6 on 2026-03-27 — step 2 has effectively been timing out for over a month, independent of the image pin issue. Bumping the overall build timeout to 3600s (60 min) gives headroom for GCB variability, keeps step 1 multi-arch pushes reliable, and leaves enough budget for the existing install-gsutil + upload flow. A follow-up PR can skip the SDK reinstall by switching the step 2 base image. Signed-off-by: Ganesh Putta <ganiredi@amazon.com>
k8s-ci-robot
pushed a commit
that referenced
this pull request
May 7, 2026
The cloud-provider-aws-push-images postsubmit has been running up against the 1200s (20 min) Cloud Build timeout: - The new gcb-docker-gcloud image (pinned in #1399) is larger and pushes/pulls take slightly longer, and GCB's shared pool has been slower overall, so step 1 (multi-arch buildx) routinely now uses 16-19 of the 20 available minutes. - Step 2 (cloudbuild-artifacts) then has almost no budget left and is killed mid-`hack/install-gsutil.sh`, which means the ecr-credential-provider binaries never reach gs://k8s-staging-provider-aws/releases/. Observed failures after #1399 landed: - release-1.36: https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/cloud-provider-aws-push-images/2051718180123971584 (step 1 ok, step 2 TIMEOUT installing gsutil) - master: https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/cloud-provider-aws-push-images/2051514822092132352 (step 1 buildkit session deadline during registry push) Cross-check: the last successful binary upload to the staging releases bucket was v1.35.1-5-g7dac1f6 on 2026-03-27 — step 2 has effectively been timing out for over a month, independent of the image pin issue. Bumping the overall build timeout to 3600s (60 min) gives headroom for GCB variability, keeps step 1 multi-arch pushes reliable, and leaves enough budget for the existing install-gsutil + upload flow. A follow-up PR can skip the SDK reinstall by switching the step 2 base image. Signed-off-by: Ganesh Putta <ganiredi@amazon.com>
k8s-ci-robot
pushed a commit
that referenced
this pull request
May 7, 2026
The cloud-provider-aws-push-images postsubmit has been running up against the 1200s (20 min) Cloud Build timeout: - The new gcb-docker-gcloud image (pinned in #1399) is larger and pushes/pulls take slightly longer, and GCB's shared pool has been slower overall, so step 1 (multi-arch buildx) routinely now uses 16-19 of the 20 available minutes. - Step 2 (cloudbuild-artifacts) then has almost no budget left and is killed mid-`hack/install-gsutil.sh`, which means the ecr-credential-provider binaries never reach gs://k8s-staging-provider-aws/releases/. Observed failures after #1399 landed: - release-1.36: https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/cloud-provider-aws-push-images/2051718180123971584 (step 1 ok, step 2 TIMEOUT installing gsutil) - master: https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/cloud-provider-aws-push-images/2051514822092132352 (step 1 buildkit session deadline during registry push) Cross-check: the last successful binary upload to the staging releases bucket was v1.35.1-5-g7dac1f6 on 2026-03-27 — step 2 has effectively been timing out for over a month, independent of the image pin issue. Bumping the overall build timeout to 3600s (60 min) gives headroom for GCB variability, keeps step 1 multi-arch pushes reliable, and leaves enough budget for the existing install-gsutil + upload flow. A follow-up PR can skip the SDK reinstall by switching the step 2 base image. Signed-off-by: Ganesh Putta <ganiredi@amazon.com>
k8s-ci-robot
pushed a commit
that referenced
this pull request
May 7, 2026
The cloud-provider-aws-push-images postsubmit has been running up against the 1200s (20 min) Cloud Build timeout: - The new gcb-docker-gcloud image (pinned in #1399) is larger and pushes/pulls take slightly longer, and GCB's shared pool has been slower overall, so step 1 (multi-arch buildx) routinely now uses 16-19 of the 20 available minutes. - Step 2 (cloudbuild-artifacts) then has almost no budget left and is killed mid-`hack/install-gsutil.sh`, which means the ecr-credential-provider binaries never reach gs://k8s-staging-provider-aws/releases/. Observed failures after #1399 landed: - release-1.36: https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/cloud-provider-aws-push-images/2051718180123971584 (step 1 ok, step 2 TIMEOUT installing gsutil) - master: https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/cloud-provider-aws-push-images/2051514822092132352 (step 1 buildkit session deadline during registry push) Cross-check: the last successful binary upload to the staging releases bucket was v1.35.1-5-g7dac1f6 on 2026-03-27 — step 2 has effectively been timing out for over a month, independent of the image pin issue. Bumping the overall build timeout to 3600s (60 min) gives headroom for GCB variability, keeps step 1 multi-arch pushes reliable, and leaves enough budget for the existing install-gsutil + upload flow. A follow-up PR can skip the SDK reinstall by switching the step 2 base image. Signed-off-by: Ganesh Putta <ganiredi@amazon.com>
k8s-ci-robot
pushed a commit
that referenced
this pull request
May 7, 2026
The cloud-provider-aws-push-images postsubmit has been running up against the 1200s (20 min) Cloud Build timeout: - The new gcb-docker-gcloud image (pinned in #1399) is larger and pushes/pulls take slightly longer, and GCB's shared pool has been slower overall, so step 1 (multi-arch buildx) routinely now uses 16-19 of the 20 available minutes. - Step 2 (cloudbuild-artifacts) then has almost no budget left and is killed mid-`hack/install-gsutil.sh`, which means the ecr-credential-provider binaries never reach gs://k8s-staging-provider-aws/releases/. Observed failures after #1399 landed: - release-1.36: https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/cloud-provider-aws-push-images/2051718180123971584 (step 1 ok, step 2 TIMEOUT installing gsutil) - master: https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/cloud-provider-aws-push-images/2051514822092132352 (step 1 buildkit session deadline during registry push) Cross-check: the last successful binary upload to the staging releases bucket was v1.35.1-5-g7dac1f6 on 2026-03-27 — step 2 has effectively been timing out for over a month, independent of the image pin issue. Bumping the overall build timeout to 3600s (60 min) gives headroom for GCB variability, keeps step 1 multi-arch pushes reliable, and leaves enough budget for the existing install-gsutil + upload flow. A follow-up PR can skip the SDK reinstall by switching the step 2 base image. Signed-off-by: Ganesh Putta <ganiredi@amazon.com>
k8s-ci-robot
pushed a commit
that referenced
this pull request
May 7, 2026
The cloud-provider-aws-push-images postsubmit has been running up against the 1200s (20 min) Cloud Build timeout: - The new gcb-docker-gcloud image (pinned in #1399) is larger and pushes/pulls take slightly longer, and GCB's shared pool has been slower overall, so step 1 (multi-arch buildx) routinely now uses 16-19 of the 20 available minutes. - Step 2 (cloudbuild-artifacts) then has almost no budget left and is killed mid-`hack/install-gsutil.sh`, which means the ecr-credential-provider binaries never reach gs://k8s-staging-provider-aws/releases/. Observed failures after #1399 landed: - release-1.36: https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/cloud-provider-aws-push-images/2051718180123971584 (step 1 ok, step 2 TIMEOUT installing gsutil) - master: https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/cloud-provider-aws-push-images/2051514822092132352 (step 1 buildkit session deadline during registry push) Cross-check: the last successful binary upload to the staging releases bucket was v1.35.1-5-g7dac1f6 on 2026-03-27 — step 2 has effectively been timing out for over a month, independent of the image pin issue. Bumping the overall build timeout to 3600s (60 min) gives headroom for GCB variability, keeps step 1 multi-arch pushes reliable, and leaves enough budget for the existing install-gsutil + upload flow. A follow-up PR can skip the SDK reinstall by switching the step 2 base image. Signed-off-by: Ganesh Putta <ganiredi@amazon.com>
10 tasks
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
3 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.
The cloud-provider-aws-push-images postsubmit has been failing across all branches (master and release-*) since early April 2026 because cloudbuild.yaml pins
gcr.io/k8s-staging-test-infra/gcb-docker-gcloud:v20221214-1b4dd4d69a, and that tag has been garbage-collected out of the staging registry. Cloud Build retries the pull 10 times and fails with 'manifest unknown: Failed to fetch "v20221214-1b4dd4d69a"'.
Example failed run (v1.36.0 tag):
https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/cloud-provider-aws-push-images/2051449456091467776
Bumping to v20260205-38cfa9523f (digest
sha256:ff388e0dc16351e96f8464e2e185b74a7578a5ccb7a112cf3393468e59e6e2d2), currently the newest tag in gcr.io/k8s-staging-test-infra/gcb-docker-gcloud and aliased to 'latest'. This image still provides /buildx-entrypoint used by the build step.
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: