Week Ending April 1, 2018

Community Meeting Summary

Rob Hirschfeld kicked off the community meeting with a demo of using Digital Rebar and Kubeadm for zero-touch Kubernetes deployment. Announcements included reminders of Meet Our Contributors this Wednesday and the Contributor Summit in Copenhagen.

The rest of the meeting was devoted to the 1.10 Release Retrospective. Release Lead Jaice DuMars congratulated the release team on getting 1.10 out only a week late despite a security update (with fallout bugs) and major issues with scalability tests. Increased automation, better staffing and better issue tracking were all cited as successes this release. Areas for improvement included:

Scalability testing needs to be checked earlier, and more people need to understand the tests. To help, SIG-Scalability is adding some presubmit tests for scalability.
Better documentation on what labels are required when and how to approve things for the milestone.
Running and checking the upgrade/downgrade tests earlier in the development cycle.
Improving the release notes process to make it less work.

Feature Work

New config parameters for Azure Load Balancer, and support for service tags.
kubectl certificate approve no longer re-checks CSRs already approved.
Server-side printing is now on by default.
Kubelet health checks are now exposed via Prometheus.
Number of PVCs requested is now considered as a factor in balancing pods across nodes.
Juju support for horizontal pod autoscaler.
The node autorizer also sets up access rules for Dynamic Kubelet Config.
All resource object statuses added to HPA description.
kubectl describe node now shows extended resources.
kubectl logs adds new –all-containers option.

Deprecated

rktnetes is all gone.

Version Updates

Other Merges

Nodes no longer schedule services prefixed with kubernetes.io if they are not exposed.
Ingress is fixed for older versions.
The Deployment controller will no longer add pod-template-hash to ReplicaSets not created by that Deployment.
kubectl now escapes percent signs.
CRI had defined behavior now for when the hostPath doesn’t exist.
Juju changed their admission controller settings.
policyConfigMapNamespace now defaults to kube-system.
System critical priority classes are available at bootstrap.
kube-scheduler --leader-elect is default True again.

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.