Stay up-to-date on Kubernetes development in 15 minutes a week.
SIG-PM (Project Management) is gone now, mostly because the chairs decided that the SIG was redundant with other SIGs, mostly SIG-Arch, but also SIG-Contribex and SIG-Usability. As part of this, SIG-PM’s subprojects, such as Enhancements, have been moved.
Timothy St. Clair has stepped down from the Steering Committee to avoid having too many VMware folks on it.
In last week’s monthly community meeting, we heard from SIG-Docs (who are moving to the Hugo Docsy theme), SIG-CLI (kubectl moving out of core), and SIG-Node (topology management and RuntimeClass). Kubernetes will be participating in the CommunityBridge Mentorships this term.
Next Deadline: Enhancements Freeze, May 5
We are well into 1.19 now, so get your KEPs and feature proposals ready for what you’re working on this term.
Last week we released updates to all supported branches: 1.16.9, 1.17.5, and 1.18.2. This update fixes a client-go regression, and requires a golang version update for 1.16 and 1.17.
Coming into 1.19 development strong with a big cleanup of developer-only dependencies. These have now been split off into their own file to both reduce repo footprint and reduce downstream dependency complexity.
Along with #90247, this adds annotation-driven codegen for tracking the lifecycle of types. The new annotations look like:
// +k8s:prerelease-lifecycle-gen:introduced=1.1
// +k8s:prerelease-lifecycle-gen:deprecated=1.8
// +k8s:prerelease-lifecycle-gen:removed=1.18
// +k8s:prerelease-lifecycle-gen:replacement=apps,v1,Deployment
and create a zz_generated.prerelease-lifecycle.go
full of useful information. If you work on any developer tooling which cares about deprecations, check this out.
kubectl version
in default namespace
from No resources found
--volume-plugin-dir
is moved to the configLast 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.