releng: Image promotion for kubernetes v1.33.0-rc.0 / v1.34.0-alpha.0

[mbianchidev]

Image promotion for kubernetes v1.33.0-rc.0 / v1.34.0-alpha.0
This is an automated PR generated from kpromo

kpromo pr --fork mbianchidev --tag v1.33.0-rc.0 --tag v1.34.0-alpha.0

/hold
cc: @kubernetes/release-engineering

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mbianchidev
Once this PR has been reviewed and has the lgtm label, please assign justaugustus for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• registry.k8s.io/images/k8s-staging-kubernetes/OWNERS

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

[jimangel]

/lgtm

[mbianchidev]

/unhold

I double checked the changes and this should be ok, according to the docs when the rc.0 is out we should promo the next alpha image too.

Waiting for approve and LGTM

[xmudrii]

/hold

[xmudrii]

@mbianchidev I have concerns about promoting two releases at the same time, we can barely promote one release at the same time (it pretty much always fails and we have to restart the job). Can you please create two separate PRs, and merge them one by one?

[mbianchidev]

@mbianchidev I have concerns about promoting two releases at the same time, we can barely promote one release at the same time (it pretty much always fails and we have to restart the job). Can you please create two separate PRs, and merge them one by one?

Roger that and while I'm at it, I will also update the docs on it.

[mbianchidev]

Opened two separate PRs instead

• releng: Image promotion for kubernetes v1.33.0-rc.0 #7971 (1.33-rc.0)
• releng: Image promotion for kubernetes v1.34.0-alpha.0 #7972 (1.34-alpha.0)

Updated docs PR: kubernetes/sig-release#2731