cloudbuild: bump timeout to 3600s

[Ganiredi]

What type of PR is this?

/kind bug

What this PR does / why we need it:

The cloud-provider-aws-push-images postsubmit has been running up against the 1200s (20 min) Cloud Build timeout. After #1399 fixed the image pin issue, step 1 (multi-arch buildx) now succeeds but consumes 16-19 of the 20 available minutes leaving step 2 (cloudbuild-artifacts) with essentially no budget. Step 2 is killed mid-hack/install-gsutil.sh, so no ecr-credential-provider binaries land in gs://k8s-staging-provider-aws/releases/.

Observed failures after #1399 landed:

• release-1.36 (step 1 ok, step 2 TIMEOUT installing gsutil): https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/cloud-provider-aws-push-images/2051718180123971584
• master (step 1 buildkit session deadline during registry push): https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/cloud-provider-aws-push-images/2051514822092132352

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. Staging image pushes continued through 2026-04-08 before the image GC killed step 1 too.

Bumping the overall build timeout to 3600s (60 min) gives:

• Headroom for GCB pool variability
• Reliable multi-arch buildx pushes on step 1
• Enough budget for the existing gsutil install + upload on step 2

Which issue(s) this PR fixes:

N/A — depends on #1399 which already landed.

Special notes for your reviewer:

No behavior change for successful builds; only raises the ceiling for slow ones. Will need cherry-picks to release-1.36 (and older release branches) once this lands so that v1.36.0 / v1.35.x / etc. postsubmits can also succeed.

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

This issue is currently awaiting triage.

If cloud-provider-aws contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

Instructions 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]

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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions 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.

[kmala]

/ok-to-test

[kmala]

/lgtm
/approve

[k8s-ci-robot]

[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

Details

Needs approval from an approver in each of these files:

• OWNERS [kmala]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment