Cut v1.37.0-alpha.1 release

[rytswd]

Scheduled to happen: Wed, 2026-06-10

Note for v1.x.0 releases: Having this issue in open state will stop the
periodic run of krel fast-forward
to avoid conflicts with releases running in parallel. The fast-forward will
automatically stop once the v1.x.0 tag is available.

Release Blocking Issues

Release Steps

• Ensure a green signal has been given by Release Signal on the day of the cut
• Create a thread on #release-management:
• Screenshot unhealthy release branch testgrid boards
• Check the health of the publishing-bot

• NoMock Run
  • Stage
  • Image Promotion PR:
  • Release
• Send email notification:
• Notify #release-management on Slack:
• Update schedule.yaml file with the latest release using schedule-builder (patch releases only)
• Collect metrics and add them to the Release steps table below through krel history --branch release-1.xx --date-from yyyy-mm-dd (current date)

Release Tools Version

❯ krel version
    __ __    ____     ______    __
   / //_/   / __ \   / ____/   / /
  / ,<     / /_/ /  / __/     / /
 / /| |   / _, _/  / /___    / /___
/_/ |_|  /_/ |_|  /_____/   /_____/
krel: The Kubernetes Release toolbox

GitVersion:    v0.21.2-0.20260610030544-f8d9e5ca5cc4
GitCommit:     f8d9e5ca5cc40956fa2aefa58e4f77e7e132d7c4
GitTreeState:  clean
BuildDate:     2026-06-10T03:05:44
GoVersion:     go1.26.4
Compiler:      gc
Platform:      linux/amd64

Release Jobs History

$ krel history --date-from 2026-06-10
INFO Running history with the following options: &{Branch:master Project:k8s-release DateFrom:2026-06-10 DateTo:2026-06-23}

STEP	COMMAND	LINK	START	DURATION	SUCCEEDED ?
mock stage	krel stage --type alpha --branch master --build-version v1.37.0-alpha.0.1408+de391ca4a4dfe6	https://console.cloud.google.com/cloud-build/builds;region=us-central1/5f7729f8-79a3-4c40-86e4-09aeeee2aa00?project=304687256732	2026-06-10T14:14:07.915049489Z	00:32:13	Yes
mock release	krel release --type alpha --branch master --build-version v1.37.0-alpha.0.1408+de391ca4a4dfe6	https://console.cloud.google.com/cloud-build/builds;region=us-central1/b6a2b585-1476-48f0-9023-40b4e6ee9f0a?project=304687256732	2026-06-10T17:45:04.414401123Z	00:11:16	Yes
stage	krel stage --type alpha --branch master --build-version v1.37.0-alpha.0.1414+f7a260bfc5521d --nomock	https://console.cloud.google.com/cloud-build/builds;region=us-central1/fcdd7e0d-0ab9-4879-9dbd-6d77e7553ff9?project=304687256732	2026-06-10T19:56:01.458220241Z	01:04:54	Yes
release	krel release --type alpha --branch master --build-version v1.37.0-alpha.0.1414+f7a260bfc5521d --nomock	https://console.cloud.google.com/cloud-build/builds;region=us-central1/70e27571-a776-4874-860a-dd7a3c4c568a?project=304687256732	2026-06-11T03:16:28.736948698Z	00:10:15	Yes

Action Items

Open Questions

/milestone v1.37
/assign @rytswd
/cc @kubernetes/release-managers
/priority important-soon
/kind documentation

[k8s-ci-robot]

@rytswd: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.

Details

In response to this:

Scheduled to happen: Wed, 2026-06-10

Note for v1.x.0 releases: Having this issue in open state will stop the
periodic run of krel fast-forward
to avoid conflicts with releases running in parallel. The fast-forward will
automatically stop once the v1.x.0 tag is available.

Release Blocking Issues

Release Steps

• Ensure a green signal has been given by Release Signal on the day of the cut
• Create a thread on #release-management:
• Screenshot unhealthy release branch testgrid boards
• Check the health of the publishing-bot

• NoMock Run
• Stage
• Image Promotion PR:
• Release
• Send email notification:
• Notify #release-management on Slack:
• Update schedule.yaml file with the latest release using schedule-builder (patch releases only)
• Collect metrics and add them to the Release steps table below through krel history --branch release-1.xx --date-from yyyy-mm-dd (current date)

Release Tools Version

❯ krel version
   __ __    ____     ______    __
  / //_/   / __ \   / ____/   / /
 / ,<     / /_/ /  / __/     / /
/ /| |   / _, _/  / /___    / /___
/_/ |_|  /_/ |_|  /_____/   /_____/
krel: The Kubernetes Release toolbox

GitVersion:    v0.21.2-0.20260609054145-c59214618768
GitCommit:     c592146187687f282a2c17a31f4a6802f58a0067
GitTreeState:  clean
BuildDate:     2026-06-09T05:41:45
GoVersion:     go1.26.4
Compiler:      gc
Platform:      linux/amd64

Release Jobs History

Step	Command	Link	Start	Duration	Succeeded?

| Stage | krel stage [arguments] | | | | |
| Release | krel release [arguments] | | | | |

Action Items

Open Questions

/milestone
/assign
/cc @kubernetes/release-managers
/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.

[rytswd]

Testgrid dashboards for master

Boards checked for FAILING:

• sig-release-master-blocking
• sig-release-master-informing

2026-06-10 14:15:43.00055285 +0000 UTC FAILING sig-release-master-informing#gce-master-scale-performance-5000 - TestGrid

sig-release-master-informing#gce-master-scale-performance-5000

comment generated by krel

[rytswd]

/milestone v1.37

[k8s-ci-robot]

@rytswd: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.

Details

In response to this:

/milestone v1.37

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.

[dipesh-rawat]

/milestone v1.37

[rytswd]

Just to make it clear, this was reported in the thread, and confirmed that it is not a blocker (ref).

[aibarbetta]

@rytswd can you update the description with the promo PR and announcement message?
We should document the krel history failure as an action item and start a discussion with release managers to troubleshoot

[rytswd]

/assign @rytswd