Post Release Branch Creation Tasks for v1.34.0-rc.0

[mbianchidev]

As a follow up on: #2824

Tasks

• Create a thread in #release-management: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1754506219434529
• Coordinate the next alpha release cut - releng: Image promotion for kubernetes v1.34.0-rc.0 k8s.io#8369
• (optional) Remove jobs for EOL versions, only if agreed upon with Release Managers - Drop k8s 1.30 jobs due to EOL test-infra#35270

• Update milestone_applier rules - Added milestone applier rules for 1.34, removed 1.30 test-infra#35271
• Update kubekins-e2e-v2/variants.yaml with the new version config - Added kubekins-e2e-v2 variants for 1.34 test-infra#35272
• Rotate configuration of release branch jobs in kubernetes/test-infra for the upcoming release Update tests config 1.34 test-infra#35273 / Update tests config 1.34 test-infra#35275
• Run test generation script and create the new release dashboards - Test jobs config and dashboards for 1.34 test-infra#35284
• Monitor the new release dashboard with the Release Signal Lead for at least 48 hours - mainly for missing or misconfigured jobs - fix 1.34 images test-infra#35288
• Add a new variant for the kube-cross image (kubernetes/release repository) and ensure the image is built and pushed properly
• Add new variants for k8s-cloud-builder and k8s-ci-builder images (kubernetes/release repository) and ensure images are build and pushed properly
• Update references in kubernetes/kubernetes with the new kube-cross image
• Update publishing-bot rules to include the new release branch - Add release-1.34 configuration publishing bot rules for v1.34 kubernetes#133447
• Ensure that a new performance tests branch is created by SIG Scalability maintainers - Create new branch release-1.34 for Kubernetes v1.34 perf-tests#3492
• Inform stakeholders about the post branch creation tasks being completed

Action Items

• Merge the docs PR.- Documentation for rc0 tasks #2819

Open Questions

/milestone v1.34
/assign @mbianchidev
/cc @kubernetes/release-managers @kubernetes/release-team-release-signal
/priority important-soon
/kind documentation

[k8s-ci-robot]

@mbianchidev: The provided milestone is not valid for this repository. Milestones in this repository: [next, v.1.25, v1.16, v1.17, v1.18, v1.19, v1.20, v1.21, v1.22, v1.23, v1.24, v1.25, v1.26, v1.27, v1.28, v1.29, v1.30, v1.31, v1.32, v1.33, v1.34]

Use /milestone clear to clear the milestone.

In response to this:

As a follow up on: #2824

Tasks

• Create a thread in #release-management:
• (optional) Remove jobs for EOL versions, only if agreed upon with Release Managers

• Update milestone_applier rules
• Update kubekins-e2e-v2/variants.yaml with the new version config
• Rotate configuration of release branch jobs in kubernetes/test-infra for the upcoming release
• Run test generation script
• Create the new release dashboards
• Monitor the new release dashboard with the Release Signal Lead for at least 48 hours - mainly for missing or misconfigured jobs
• Add a new variant for the kube-cross image (kubernetes/release repository) and ensure the image is built and pushed properly
• Add new variants for k8s-cloud-builder and k8s-ci-builder images (kubernetes/release repository) and ensure images are build and pushed properly
• Update references in kubernetes/kubernetes with the new kube-cross image
• Update publishing-bot rules to include the new release branch
• Ensure that a new performance tests branch is created by SIG Scalability maintainers
• Coordinate the next alpha release cut -
• Inform stakeholders about the post branch creation tasks being completed

Action Items

Open Questions

/milestone
/assign
/cc @kubernetes/release-managers @kubernetes/release-team-release-signal
/priority important-soon
/kind documentation

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.

[mbianchidev]

/milestone v1.34

[mbianchidev]

/assign @mbianchidev

[drewhagen]

Added a new PR that replaces the placeholder for the prow image:
kubernetes/test-infra#35275

[drewhagen]

Added a new PR that updates the testgrid dashboards:
kubernetes/test-infra#35276

[drewhagen]

Ran the test generation script and added a new PR that updates the jobs:
kubernetes/test-infra#35277

Signing off for the night 🫡 cc: @mbianchidev

[mbianchidev]

Merging order to make it work should be:
kubernetes/test-infra#35275
kubernetes/test-infra#35277 (fails for couldn't find dashboard "sig-release-1.34-informing" for job "ci-kind-dra-1-34")
kubernetes/test-infra#35276 (fails for couldn't find dashboard "sig-release-1.30-blocking" for job "ci-kubernetes-build-1-30")

All the above PRs were trial and errors, this was the actual one that worked: kubernetes/test-infra#35284

Then, lower prio, these:
kubernetes/test-infra#35270
kubernetes/test-infra#35271

[mbianchidev]

Add a new variant for the kube-cross image (kubernetes/release repository) and ensure the image is built and pushed properly has been done previously