Cut v1.27.15 release
Verolop opened this issue · 4 comments
Scheduled to happen: Tue, 2024-06-11
Release Blocking Issues
Release Steps
- Create a thread on #release-management: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1718095472649639
- Screenshot unhealthy release branch testgrid boards
- Check the health of the publishing-bot
- Mock Run
- Stage
- Release
- NoMock Run
- Stage
- Image Promotion: kubernetes/k8s.io#6882
- Release
- Notify #release-management: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1718165801825349?thread_ts=1718095472.649639&cid=CJH2GBF7Y
- Send notification: https://groups.google.com/a/kubernetes.io/g/dev/c/WQzWaAw2sBI?pli=1
- Update
schedule.yaml
file with the latest release usingschedule-builder
- Collect metrics and add them to the
Release steps
table below
Release Tools Version
krel: The Kubernetes Release toolbox
GitVersion: v0.16.5
GitCommit: 8ce5e1592ec03b8bf2e5a3b8b97fcc8e6684e9df
GitTreeState: clean
BuildDate: 2024-06-11T16:51:26
GoVersion: go1.21.1
Compiler: gc
Platform: darwin/arm64
Release Jobs History
Step | Command | Link | Start | Duration | Succeeded? |
---|---|---|---|---|---|
Mock stage | krel stage --type official --branch release-1.27 |
https://console.cloud.google.com/cloud-build/builds/b285b431-8db9-4b11-a258-781512962b52?project=kubernetes-release-test | June 11, 2024 at 7:18:19 PM UTC+1 | 55 min 10 sec | YES |
Mock release | krel release --type official --branch release-1.27 --build-version v1.27.12-18+7c861b1ecad97e |
https://console.cloud.google.com/cloud-build/builds/d1ffafc8-1c41-4856-ac6f-13addc3de495?project=kubernetes-release-test | June 11, 2024 at 8:23:31 PM UTC+1 | 16 min 24 sec | YES |
Stage | krel stage --type official --branch release-1.27 --build-version v1.27.12-18+7c861b1ecad97e --nomock |
https://console.cloud.google.com/cloud-build/builds/dc37515e-75c8-4a12-941a-0ee2b180ec82?project=kubernetes-release-test | June 11, 2024 at 8:45:13 PM UTC+1 | 1 hr 27 min | YES |
Release | krel release --type official --branch release-1.27 --build-version v1.27.12-18+7c861b1ecad97e --nomock |
https://console.cloud.google.com/cloud-build/builds/0a7185d0-ac15-4ac2-b5be-eac267230aa0?project=kubernetes-release-test | June 11, 2024 at 11:48:03 PM UTC+1 | 15 min 19 sec | YES |
Action Items
Open Questions
/milestone
/assign
/cc @kubernetes/release-managers
/priority important-soon
/kind documentation
@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:
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 with the latest release usingschedule-builder
- Collect metrics and add them to the
Release steps
table belowRelease 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.
/milestone v1.27
The release is done, so closing this issue.
I have updated the issue description.
/close
@mehabhalodiya: Closing this issue.
In response to this:
The release is done, so closing this issue.
/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.