This week’s demo was Stork, a tool for managing “hyperconverged” storage in Kubernetes. The community meeting then continued with release updates, the graph, and some SIG updates. Architecture is working on implementing the subproject proposal explained in last week’s issue. Bob Wise of Scalability did a presentation where he explained that the SIG will be focusing just on preventing scalability regressions, and has no concrete plans to push Kubernetes clusters beyond 5000 nodes in size. If you want bigger clusters, contribute to the SIG. They also have a new charter. Scheduling is promoting priority and preemption to Beta status, optimizing Affinity, and designing a new extension model for the scheduler. They also mentioned three “incubator” projects, Kube-arbitrator, Cluster capacity tool, and Descheduler.
We are now in week 7 of the 1.10 release cycle. Feature freeze has passed, file an exception if you missed the deadline. This week, we will be cutting the first Beta release and creating the Release branch.
The next deadline is Code Slush on February 20th. The release lead warns contributors that the schedule will be enforced.
This week’s graph, per Tim Pepper, is feature activity on issues. You can track feature activity here through the release cycle, including how feature activity is “back-loaded”, where most happens near each deadline (Feature Freeze, Code Freeze, Release).
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.