cloudbuild: upgrade to E2_HIGHCPU_32 to fix session timeout#1421
Conversation
Multi-arch builds (linux/amd64 + linux/arm64) take ~12 min on N1_HIGHCPU_8, causing the BuildKit session to expire before the push phase completes: error: no active session: context deadline exceeded Other K8s repos with large multi-arch binaries (aws-ebs-csi-driver, cloud-provider-gcp) use E2_HIGHCPU_32 which completes builds in ~3-5 min, well within the session window.
|
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. |
|
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. |
|
/ok-to-test |
|
/release-note-none |
|
/test pull-cloud-provider-aws-e2e-kubetest2-quick |
|
/lgtm |
|
[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 |
…-upstream-release-1.36 Automated cherry pick of #1421: cloudbuild: upgrade to E2_HIGHCPU_32 to fix session timeout
Multi-arch builds (linux/amd64 + linux/arm64) take ~12 min on N1_HIGHCPU_8, causing the BuildKit session to expire before the push phase completes:
error: no active session: context deadline exceededOther K8s repos with large multi-arch binaries (aws-ebs-csi-driver, cloud-provider-gcp) use E2_HIGHCPU_32 which completes builds in ~3-5 min, well within the session window.
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?: