Cut v1.29.8 release

[jeremyrickard]

Scheduled to happen: Wed, 2024-08-14

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

• [x] Create a thread on #release-management: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1723654886778929
• [x] Screenshot unhealthy release branch testgrid boards
• [x] 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/7176
  • [x] Release
• [x] Notify #release-management: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1723686773969729?thread_ts=1723654886.778929&cid=CJH2GBF7Y
• [x] Send notification: https://groups.google.com/g/kubernetes-announce/c/bB8W6MYQXis/m/eQvR6jlKBgAJ
• [ ] Update schedule.yaml file with the latest release using schedule-builder https://github.com/kubernetes/website/pull/47510
• [x] Collect metrics and add them to the Release steps table below

Release Tools Version

GitVersion:    v0.17.2
GitCommit:     186460da117ffa56aa85b53ee6b2dbc746fc8dcb
GitTreeState:  clean
BuildDate:     2024-08-14T07:41:53
GoVersion:     go1.22.5
Compiler:      gc
Platform:      darwin/arm64

Release Jobs History

STEP	COMMAND	LINK	START	DURATION	SUCCEEDED?
mock stage	krel stage --type official --branch release-1.29 --build-version v1.29.7-23+ff6fbfcb41150d	https://console.cloud.google.com/cloud-build/builds/5255fcc3-b45f-4648-95df-a303cd4c4829?project=648026197307	2024-08-14T17:47:15.815646473Z	00:56:31	Yes
mock release	krel release --type official --branch release-1.29 --build-version v1.29.7-23+ff6fbfcb41150d	https://console.cloud.google.com/cloud-build/builds/f6daabaf-4592-4458-bf3f-f8f352c2e900?project=648026197307	2024-08-14T18:47:49.793638028Z	00:15:12	Yes
stage	krel stage --type official --branch release-1.29 --build-version v1.29.7-23+ff6fbfcb41150d --nomock	https://console.cloud.google.com/cloud-build/builds/3ab5fefe-01aa-4e1f-9d7d-f967fe75ea6a?project=648026197307	2024-08-14T19:34:44.929348119Z	01:22:37	Yes
release	krel release --type official --branch release-1.29 --build-version v1.29.7-23+ff6fbfcb41150d --nomock	https://console.cloud.google.com/cloud-build/builds/85e19da9-9185-4cfc-854e-02b90b76885f?project=648026197307	2024-08-15T01:01:03.547510669Z	00:18:21	Yes

Action Items

Open Questions

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

[jeremyrickard]

Testgrid dashboards for 1.29

Boards checked for FAILING:

• sig-release-1.29-blocking
• sig-release-1.29-informing

2024-08-14 17:15:22.526353 +0000 UTC FAILING sig-release-1.29-blocking#gce-cos-k8sstable2-alphafeatures - TestGrid

sig-release-1.29-blocking#gce-cos-k8sstable2-alphafeatures

2024-08-14 17:15:22.526353 +0000 UTC FAILING sig-release-1.29-informing#gce-cos-k8sstable2-serial - TestGrid

sig-release-1.29-informing#gce-cos-k8sstable2-serial

comment generated by krel

[jeremyrickard]

After discussion with @dims and @BenTheElder, we will proceed with the 1.29 release. See https://kubernetes.slack.com/archives/CJH2GBF7Y/p1723656088321359 for more info

We will track some post-release test update issues.

[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]

/close

[k8s-ci-robot]

@xmudrii: Closing this issue.

In response to this:

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