Cut v1.x.y-{alpha,beta,rc}.z release

[cutiepie331979-rgb]

Scheduled to happen:

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
• Mock Run
  • Stage
  • Release
• 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

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
/assign
/cc @kubernetes/release-managers
/priority important-soon
/kind documentation

[k8s-ci-robot]

@cutiepie331979-rgb: 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.

In response to this:

Scheduled to happen:

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
• Mock Run
• Stage
• Release
• 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

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