Week Ending June 14, 2020

Developer News

The 1.19 release schedule has been changed, see below.

The Github admin team asks folks not to rename the default branch for community repos until they can plan how to make that work with automation.

Kubecon Boston CfP has been extended to June 28th.

Release Schedule

Next Deadline: Placeholder Doc PRs, June 19th

To celebrate this Juneteenth, the Docs team says you need to open an initial PR for your new feature docs. Maybe do it early so you free up your Friday for other things.

The 1.19 schedule has been changed, with Code Freeze now on July 9, and Cherry Pick and Test Freeze deadlines on August 6th. Beta 2 is available for your testing.

Patch releases for all versions (1.16, 1.17, 1.18) will be published this Thursday.

Merges

IPv6 dual-stack becomes a thing on Windows
Load balancers can be scheduled to unschedulable nodes, so change your settings in 1.19 if you don’t want them
client-go can show server-side warnings
Scheduler plugins can log cluster events
Support floating IPv6 on Azure load balancers
Default admission webhooks are now actually enabled
kubeadm join gets a retry loop
No more off-by-one errors with AWS network interfaces
Feature gate DefaultPodTopologySpread uses the PodTopologySpread plugin with a default config
Clear nominatedNodeName if the node is deleted
Change how we reset fields to sending empty lists/items
CSI volume attachment starts using shared informers for scalability
It’s time to migrate your in-tree vSphere volumes to the CSI driver
kubectl run --privileged

Promotions

RotateKubeletClientCertificate to GA
SCTPSupport is beta, and enabled by default

Deprecated

Watchcache’s --target-ram-md, now nonfunctional, shuffles off
kubelet --experimental-allocatable-ignore-eviction deprecated since it’s in the config file

Version Updates

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.