Cut v1.32.3 release

[jeremyrickard]

Scheduled to happen: Tue, 2025-03-11

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

• [ ] Create a thread on #release-management:
• [ ] Screenshot unhealthy release branch testgrid boards
• [ ] Check the health of the publishing-bot
• Mock Run
  • [ ] Stage
  • [ ] Release
• NoMock Run
  • [ ] Stage
  • [ ] Image Promotion:
  • [ ] Release
• [ ] Notify #release-management:
• [ ] Send notification:
• [ ] Update schedule.yaml file with the latest release using schedule-builder
• [ ] Collect metrics and add them to the Release steps table below

Release Tools Version

GitVersion:    vM.m.p
GitCommit:     191ddd0b0b49af1adb04a98e45cebdd36cae9307
GitTreeState:  clean
BuildDate:     YYYY-MM-DDTHH:mm:ssZ
GoVersion:     go1.16.3
Compiler:      gc
Platform:      linux/amd64

Release Jobs History

Step	Command	Link	Start	Duration	Succeeded?
Mock stage	krel stage [arguments]
Mock release	krel release [arguments]
Stage	krel stage [arguments]
Release	krel release [arguments]

Action Items

Open Questions

/milestone v1.32 /assign @jeremyrickard @Verolop /cc @kubernetes/release-managers /priority important-soon /kind documentation

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[xmudrii]

@jeremyrickard @Verolop Can you please fill and close this issue?

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[xmudrii]

/remove-lifecycle rotten /close

[k8s-ci-robot]

@xmudrii: Closing this issue.

In response to this:

/remove-lifecycle rotten /close

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.