Week Ending Feburary 12, 2018

You may now subscribe to LWKD by email using MailChimp. We also have a Twitter account.

Community Meeting Summary

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.

Brendan Burns went over some of the changes to repos outlined in the last issue. The project is continuing Meet Our Contributors sessions the first Wednesday of every month, and needs volunteers.

Release Schedule

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.

Feature Work

• The Local Volumes Plugin now has block volume support.
• CRI now uses the mountpoint as a storage identifier. This may cause some backwards-compatibility issues, especially for devicemapper. CRI has also made backwards-incompatible changes to support shared PID namespaces.
• Auditing is enabled behind a feature gate.
• All workloads (Deployment, ReplicaSet, etc.) are now stored in etcd in apps/v1 format.
• PersistentVolumes have more measurements now.
• Custom resources now support prometheus metrics.
• Context data is now present for all relevant cloud APIs. as part of a general effort to carry context all through Kubernetes.
• Added a generic cache for loadbalancer data on Azure, and auto-deletion of abandoned IP addresses.
• Key Management Service plugins now speak gRPC.
• MountPropagation is now Beta.
• The certificate controller can delete CSRs for cleanup purposes.
• There are now volume metrics on vSphere.
• KubeAdm added an imagePullPolicy option to init config and an option to not taint the master.
• Ceph volumes can now use a keyring parameter.
• AWS attach/detach is faster.

Deprecated

• The KubeletConfiguration.ConfigTrialDuration config field has been removed.
• You can’t name PriorityClasses starting with “system-“ anymore.
• The –service-sync-period flag has been removed from the controller-manager.
• persistentVolumeReclaimPolicy of “Recycle” is being deprecated.

Version Updates

• Calico to Version 2.6.7.

Other Merges

• All Kubernetes project containers can now be pulled from k8s.gcr.io.
• Kubelet is only registering API sources when connecting, allowing standalone Kubelets to stop hanging forever.
• The scheduler now only uses the default predicate/prioritizer if they are unspecified in the policy config, retroactive to 1.9.
• “none” is now an option for EnforceNodeAllocatable.
• The scheduler can take a config file without a ConfigMap now.
• Pod priority will be silently ignored if disabled.
• Windows nodes have more accurate memory reporting.

Graph of the Week

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 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.