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.
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:
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.
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).
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.
Most changes below are for v1.17:
Close one symlink security hole with in
kubectl cp, by controlling the order in which the symlinks are unpacked
- v1.17 API servers can demand only v1 AdmissionReview and ConversionReview requests
livezinclude etcd and kms health checks
- Don’t publish or validate OpenAPI client-side for CRDs that have unknown fields (backported)
- Stop logging closed proxy connections
- Deployments, ReplicationControllers, and Jobs all get TerminationGracePeriods
- Context is the first argument of Schedule()
Original Source: http://lwkd.info/2019/20190917