Week Ending May 16, 2021

Developer News

Security alerts:

CVE-2021-25736 reported by Eric Paris and Christian Hernandez, permits re-routing Windows proxy traffic, but does not affect Linux. Fixed in all active Kubernetes releases.
CVE-2021-25737 reported by John Howard, allows a similar hijacking of traffic by users who can manipulate EndpointSlices. Also fixed in all active Kubernetes releases.
CVE-2021-25738 reported through our bug bounty by Jordy Versmissen, permits code injection through the Java client via YAML hacking. Fixed in 12.0 and 11.0.1 updates of the Java client.

SIG-Release is talking about setting the release cycle dates a year in advance and would love your feedback on the topic.

Release Schedule

Next Deadline: Exception Requests and Feature Blog items due June 28th

Enhancements freeze is now in effect, so if you have a major feature that’s not yet listed you need to file an exception with the release team.

Update versions 1.21.1, 1.20.7, 1.19.11, and 1.18.19 are now available. As mentioned, this is the last update for 1.18, and primarily contains the priority/fairness fix for that version. The 1.21 update includes fixes for recently reported CVEs. Next patch releases are due out June 16.

Other Merges

kubectl describe shows when binary data is stored in a ConfigMap
The Watch Order Conformance Test now tests what it’s supposed to
Don’t collect accelerator metrics if the user has said not to
kubectl set works for init containers
Creation/Deletion timestamps are now populated in fuzzing tests

Structured Logging Migration: IPVS proxy instrumentation

Promotions

NamespaceSelector affinity to Beta

Deprecated

Since kubeconfig hasn’t been alpha for a while, kubeadm alpha kubeconfig has been replaced
Kubeadm only does CoreDNS, so we don’t need ClusterConfiguration.DNS.Type anymore

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.