Last Week in Kubernetes Development: Week Ending September 15, 2019

Developer News

San Diego contributor summit registration is open and already 50% full, so don’t wait to register.

Steering Committee candidates have posted their platforms; voting begins September 18th.

Kubernetes users on Discuss need your help! Win swag by answering questions.

Release Schedule

Next Deadline: 1.16.0 Release, September 18th

We will release version 1.16 this Wednesday, which is a two-day delay from the original Sept. 16th deadline, in order to check CI Signal stability. Keep TestGrid Green!

Several update releases were scheduled for Sept. 18, but may be delayed due to the major release:

  • 1.15.4
  • 1.14.7
  • 1.13.11

Featured PRs

enhancements#807: kubernetes-csi release process

The CSI team has nicely formalized a lot of the release management process. CSI has historically had a more ad-hoc release process so it’s great to see things getting solidified and more bidirectional testing between k/k and CSI.

test-infra#14296: start run books

Hopefully the first of many, the SIG-Testing team now has a place for recording operational knowledge for the tooling that keeps Kubernetes flying. If you’re interested in writing (or co-writing) a runbook on one of the testing tools, please reach out to SIG-Testing (though probably after Wednesday).

#82514: Exec probes should not be unbounded

A relatively simple cleanup, this PR and the corresponding fix for HTTP probes help to improve stability in strange edge cases. While a probe with never-ending output would likely not be the easiest attack vector, always be careful with user-controlled runtime data and don’t assume standards compliance or reasonableness.

Other Merges

Most changes below are for v1.17:

Original Source: http://lwkd.info/2019/20190917