Cut 1.26.15 release

[Verolop]

Scheduled to happen: Wed, 2024-03-13

Release Blocking Issues

Release Steps

• Create a thread on #release-management: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1710355231652309
• Screenshot unhealthy release branch testgrid boards
• Check the health of the publishing-bot
• Mock Run
  • Stage
  • Release
• NoMock Run
  • Stage
  • Image Promotion: releng: Image promotion for kubernetes v1.26.15 k8s.io#6576
  • Release
• Notify #release-management: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1710533153421119?thread_ts=1710355231.652309&cid=CJH2GBF7Y
• Send notification: https://groups.google.com/g/kubernetes-announce/c/Flf-scI_eFs/m/TIujtsQnBgAJ
• Update schedule.yaml file with the latest release
• 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]	https://console.cloud.google.com/cloud-build/builds/5ec3f62c-a03d-4a15-9a13-12de613fc550?project=kubernetes-release-test			YES
Mock release	krel release [arguments]	https://cloudbuild.googleapis.com/v1/projects/kubernetes-release-test/locations/global/builds/714b8d8f-433a-4687-9d28-bdf98ed9236f			YES
Stage	krel stage [arguments]	https://console.cloud.google.com/cloud-build/builds/4c826bed-e497-4fb7-905e-6b16381d85ce?project=648026197307			YES
Release	krel release [arguments]	https://console.cloud.google.com/cloud-build/builds/177242fa-3198-4575-87dc-952f3ac96b61?project=648026197307			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:

Scheduled to happen: Wed, 2024-03-13

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
• 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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jeremyrickard]

/milestone v1.26

[saschagrunert]

@Verolop do you mind updating the docs in the first comment and then close this one?

[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

[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