SIG-Release will be meeting 9/22 to discuss reopening full development by removing the 1.20 milestone restriction. If you have opinions on this, please attend.
The Steering Committee election is in progress, please vote. If you didn’t get your ballot, request a replacement. Also, we are planning to replace CIVS for Kubernetes elections in the future, and we have a CommunityBridge project about it, so encourage eligible interns to apply.
Next Deadline: Enhancements Freeze, October 6th
1.19.2,1.18.9, and 1.17.12 were released last Wednesday, with a host of bugfixes, primarily to EndpointSlice functionality and Azure support. Also v1.19 was upgraded to Go 1.15.2 to incorporate golang bugfixes.
A possibly breaking change if you were doing something very weird in a custom controller, the status and scale subresources will no longer accept changes to
metadata.managedFields. This will ensure that intentional manual changes must all flow through the main resource API.
A simple change, now
kubectl wait --for=delete will not exit with a failed exit code if the object doesn’t exit. This is mostly aimed at simplifying cleanup scripts that call several deletes and then wait for them all to complete. Previously if a delete finished quickly, that could throw things out of whack. Now it will do the expected thing even in that race condition case.
apiserver_request_duration_secondsto take request latency into account, with graphs!
etcd_object_countsby identifying the end of a key; we’ll see if this breaks anything
kubectl port forwardworks with TCP and UDP together, again
kubeadm upgrade node --kubelet-versionflag removed
kubadm alpha kubelet config enable-dynamicin 1.20
Last Week In Kubernetes Development (LWKD) is a product of some members of the Kubernetes project, but is not an official publication of the Kubernetes project or the CNCF. 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.