LWKD logo

Last Week in Kubernetes Development

Stay up-to-date on Kubernetes development in 15 minutes a week.

Subscribe
Twitter
RSS

View LWKD on GitHub

Week Ending March 15, 2020

Developer News

The March Community Meeting will be this Thursday.

Release Schedule

Next Deadline: Code Thaw, March 17th; Cherry Pick Deadline March 19

We’re going into Code Thaw now, so remember you need to tag any fixes with branch v1.18. Your docs should be already complete (they are, aren’t they?), and 1.18rc1 will be released on Tuesday. Final release is still slated for March 24th.

All supported versions were just updated on March 12, including v1.15.11, v1.16.8, and v1.17.4. Note that this release upgrades the required Golang version.

#89056: EndpointSlice and Endpoints behavior for terminating pods should be the same

It’s been a quiet week thanks to code freeze so starting off with a small but useful fix. For those playing around with the new EndpointSlices system, you no longer have to filter out terminating pods. If you haven’t checked out EndpointSlices, this is great time to!

#88959: Fix for #77733 (NodeLifecycleController is overloading kube-apiserver) into release-1.16

We don’t normally cover backports, but as the mainline fix was spread over many PRs this is easier to link to. The core issue was too many nodes going unready simultaneously could overwhelm apiserver/etcd due to the number of updates involved in marking a node NotReady. Collectively these fixes massively improve the performance of that NotReady transition and so decrease the chances of a self-DoS. It has also been backported to all other versions, the linked PR is just an example. The underlying fixes are listed below.

Other Merges

Version Updates

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.