Please migrate your test jobs off the old Prow Default Cluster as soon as you can, please.
The Kubernetes Contributor Summit Chicago is looking for event volunteers to help run the Summit. Note that you must be a Kubernetes contributor to be eligible.
Next Deadline: Enhancements Due, June 16th (01:00 UTC)
Hopefully you opted in your Enhancements for Production Readiness Review, so by this Thursday you’ll have a completed, or at least in-progress, PRR. If not, you’re going to need to seek an Exception.
Patch releases, including a go version bump are expected out this Wednesday.
SIG-Node has added some documentation to
k/k to clarify how CRI as a library and standard will be versioned over time, and how Kubernetes should interact with it. This solidifies the use of SemVer in a similar way as Kubernetes itself and a similar N-3 version skew compatibility rule. It also includes a changelog back through CRI v1 being introduced in Kubernetes 1.20. For both developers and CRI admins, this document is well worth a read to better understand the goals for how CRI will evolve over time.
Support for cgroups v2 went GA back in 1.25 but one new feature we haven’t previously made use of is the cgroup-aware OOM support added in kernel 4.19. In short, this mode means that if any task in a cgroup is selected for OOM termination, the whole group is terminated. This avoids common issues with things like forking web servers where a subprocess inside the container OOMs but Kubernetes is unaware of this because PID 1 keeps running. Some tools handle this internally but most don’t and either blindly retry the failing operation or, in the worst cases, corrupt some internal state.
rest.DefaultServerUrlForis reusable now for easy URL generation
--azure-container-registry-configis deprecated; use Credential Providers instead
--provider-id flaghas been un-deprecated; we need it after all
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.