The 2023 Steering Committee Election has started, with Nominations. Do you want to run for Steering? Of course you do, nominate yourself by August 26. Also, all contributors should check if they are eligible to vote by logging into elections.k8s.io and seeing if it says “Eligible”. If it doesn’t, and your should be eligible, file an exception.
Next Deadline: RC1 released, August 10
We are in the final countdown to releasing Kubernetes 1.28 on the 15th; test grid looks mostly OK. Your part of that, aside from responding rapidly to any test failures, is to try out running the RC in your test environment so we can catch any last-minute, showstopper usability issues.
Patch releases for all supported versions should be out this week. They will include Yet Another GoLang Update.
This KEP adds a new field to the Kubernetes Jobs API which lets users specify if they want the pods of a job to be recreated as soon as the previous pods are terminating, or only once they’ve fully terminated. In 1.27, a job is considered to be failed as soon as the job’s pods are in terminating state. This KEP lets the user control this behaviour and let them mark the job as failed only after the pods have been terminated. It adds two new API fields, one for configuring whether or not to wait for the terminating pods to finish before creating replacement pods, and another field in Status for tracking the number of terminating pods. This would ensure that the number of pods that are running in the cluster would be the same as what the user specifies at any given time, and hence prevent unnecessary scaling up of the cluster. This KEP was created on April 4th, 2023 by Kevin Hannon and is in alpha in the 1.28 release.
Last Week In Kubernetes Development (LWKD) is a product of multiple contributors participating in Kubernetes SIG Contributor Experience. All original content is licensed Creative Commons Share-Alike, although linked content and images may be differently licensed. LWKD does collect some information on readers, see our privacy notice for details.
You may contribute to LWKD by submitting pull requests or issues on the LWKD github repo.