Cut v1.30.2 release

[Verolop]

Scheduled to happen: Tue, 2024-06-11

Release Blocking Issues

Release Steps

• [x] Create a thread on #release-management: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1718095830664929
• [ ] Screenshot unhealthy release branch testgrid boards
• [ ] Check the health of the publishing-bot
• Mock Run
  • [x] Stage
  • [x] Release
• NoMock Run
  • [x] Stage
  • [x] Image Promotion: https://github.com/kubernetes/k8s.io/pull/6885
  • [x] Release
• [x] Notify #release-management: Link to Slack
• [x] Send notification: https://groups.google.com/a/kubernetes.io/g/dev/c/4_P3xiJyuOQ
• [ ] Update schedule.yaml file with the latest release using schedule-builder
• [x] 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 --type alpha --branch release-1.30	https://console.cloud.google.com/cloud-build/builds/9969c16d-488b-40d5-bbed-df6a2872157d?project=kubernetes-release-test		00:48:22	Yes, but at the moment, Go security updates are not done. We still have cherry-picks that are not merged.
Mock stage	krel stage --type alpha --branch release-1.30	https://console.cloud.google.com/cloud-build/builds/b2ced4a8-7089-4d08-a05c-4d82036f2c0d?project=648026197307		01:05:51	YES
Mock release	krel release --type official --branch release-1.30 --build-version v1.30.1-30+60f96f58189dae	https://console.cloud.google.com/cloud-build/builds/2f1d2049-316c-4de9-b210-d6c8e0b85efe?project=648026197307		00:17:42	YES
Stage	krel stage --type official --branch release-1.30 --build-version v1.30.1-30+60f96f58189dae --nomock	https://console.cloud.google.com/cloud-build/builds/f9440d8f-280d-4481-96b1-f5f656ad94d3?project=648026197307		01:23:53	YES
Release	krel release --nomock --type official --branch release-1.30 --build-version v1.30.1-30+60f96f58189dae	https://console.cloud.google.com/cloud-build/builds/03ec8ba0-97bf-4baf-a069-cb6a495bab82?project=648026197307		00:17:02	YES

Action Items

Open Questions

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

[k8s-ci-robot]

@Verolop: 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]

Use /milestone clear to clear the milestone.

In response to [this](https://github.com/kubernetes/sig-release/issues/2525): >## Scheduled to happen: Tue, 2024-06-11 > >## 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](https://github.com/kubernetes/website/blob/main/data/releases/schedule.yaml) with the latest release using [`schedule-builder`](https://github.com/kubernetes/release/tree/master/cmd/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 >/assign >/cc @kubernetes/release-managers >/priority important-soon >/kind documentation > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[mehabhalodiya]

The release is done, so closing this issue. I have updated the issue description.

/close

[k8s-ci-robot]

@mehabhalodiya: Closing this issue.

In response to [this](https://github.com/kubernetes/sig-release/issues/2525#issuecomment-2171035056): >The release is done, so closing this issue. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.