Stay up-to-date on Kubernetes development in 15 minutes a week.
It’s Kubecon Week! And there’s a ton of Kubernetes community sessions scheduled. See the end of LWKD for a full list.
Security Advisory: contributor Qin Ping found a way for unauthorized users to crash your backups via VolumeSnapshot. Fix this by either restricting access to the snapshot storage API, or by upgrading to snapshot-controller v3.0.2.
GitHub is having as-yet-unexplained fetch errors with some PRs. This is affecting builds and messed up the release of 1.18.11.
SIG-CLI has promoted Eddie Zaneski to Lead, and Tim Pepper has stepped down from SIG-Release to be replaced by Sascha Grunert and Dan Mangum.
Please share your feedback on how the Triage Workflow changes are working for you.
Next Deadline: Docs ready by Nov. 23
We are in Code Freeze, so hopefully you got your PRs in – 45 enhancements made it. Aside from the conference, you should be focused entirely on fixing test failures and finishing up docs. Have those ready to review by Nov. 23, and to merge by (postponed) Dec. 2.
Due to the issue with Github, the v1.18.11 packages were unusable, and had to be replaced by v1.18.12 last Thursday. v1.17.14 and v1.19.4 were also released, on schedule.
--experimental-logging-sanitization
flag/metrics/resources
endpoint for pods, including CPU and Memory metrics, lets you check what your pods are actually consumingrequestAbortsTotal
, vSphere version, Node Authorizer loadWindowsContainerResources
to the CRI APIservice.spec.topologyKeys
; who knew?Accept-Encoding
header removed from HTTP readiness probeskubelet_runtime_operations_seconds
for monitoring slow pullsdiscovery.k8s.io/v1alpha1
API is deprecated, all in one PR, whew!The following sessions are given by SIGs, WGs, or other community groups inside kubernetes:
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.