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 Feburary 18, 2018

Community Meeting Summary

This week’s Community Meeting demo was AppZ by Cloudbourne, a proprietary online source-to-production development and deployment service based on Kubernetes. Jaice DuMars gave an update on the 1.10 timeline, and 19.3 and 1.8.8 have been released. 1.9.4 is expected about two weeks from the meeting.

Aaron Crickenberger offered an update from SIG-Testing, announcing that Jenkins is no longer used in the project’s Github development, having been entirely replaced by the Kubernetes-native Prow. He thanked Amazon for hosting a Testing face-to-face in Seattle January 26th. He reminded people about Testing Commons, went over some Prow UI updates, and discussed implementation of Tide, a tool designed to replace the submit queue. Testing would like to set firm criteria for blocking test failures, and they’re looking for help implementing Docker-on-Docker in the test infrastructure so that they can simulate a cloud without needing to run one for every E2E test.

Paris Pittman of SIG-Contribex also had many updates, including a work on a new charter and the Contributor Guide, which will be merged into kubernetes.io. The mentoring subproject needs contributors, particularly more mentors for Outreachy, GSOC, Meet Our Contributors and SIGs that can devote time to group mentoring. They’re also working on a User Guide for DevStats graphs, Issue Triage guidelines, and Slack usage guidelines, and would like feedback from contributors on all of these. Contribex is having a face-to-face this week, will be doing a “SIGs Roadshow”, and wants to remind everyone about the Copenhagen Contributor Summit.

SIG-API-Machinery, whose Daniel Smith reminds everyone that they don’t spec the API, they just plumb it, would like feedback on their Advanced Configuration Management design proposal.

Finally, the meeting began an important discussing into the functioning of LGTM and Approval labels. Currently automation settings trigger “auto-approval” of merges when the submitter is an owner. This has caused some SIGs and repos to accidentally merge things that weren’t ready. What should the correct behavior be, and should it be configurable by repository? Please add your thoughts on the issue.

KubeVirt Meeting Summary

Network Device Plugin work in order to get network resources into a pod using a device plugin. Still early research but it’s progressing.

Release Schedule

Last week was Week 7 of 12 for 1.10 development, and included a beta release and setting up the release branch. Tuesday the 20th will begin Code Slush, where issues and features need to get ready for final merge on Code Freeze. All issues in the milestone are considered release-blocking until removed. Currently there are 48 issues open in the milestone.

Feature Work

Deprecated

Version Updates

Other Merges

Other Repositories

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.