ICYMI, Kubernetes 1.20 has been released. This particular release has 42 major enhancements, making it the most featureful release in a while, and probably the most disruptive as well. Maybe use the holidays for testing instead of deploying it on Christmas Eve. Just a tip.
The chairs of the Component Standard WG are retiring and are looking for new leaders for that WG.
Next Deadline: 1.21 cycle begins, January 5th
We are currently in the limbo period between the release of 1.20 and the start of official 1.21 development, otherwise known as “packaging up 1.20.1”. Expect an announcement of the start of 1.21 after New Year’s, and even consider being a release team shadow.
A good reminder and example of updating code using the old
failure-domain.beta.kubernetes.io labels, this PR switches a lot of systems over to the newer
topology.kubernetes.io equivalents. If you’ve been putting off a similar update in your in-tree code or external automation, now is a great time to start!
If you use the AlwaysPullImages admission controller, this should ease switching pains when enabling it. Previously all pods would have to be recreated due to imagePullPolicy being an immutable field, now updates to existing pods created before enabling the admission plugin will still be updatable except to change their image.
To improve usability by humans,
kubectl logs -l will now display an error banner if no pods match the requested label selector. If you use commands like that in automation, notably in CI jobs where the pods don’t always exist yet, be sure to check for compatibility.
kubectl logs --tail #are now repeatable
--allocate-node-cidrsby side effect, are set only by
Service.topologyKeysis deprecated in 1.21, to be replaced by Topology Aware Subsetting
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.