LWKD logo

Last Week in Kubernetes Development

Stay up-to-date on Kubernetes development in 15 minutes a week.


View LWKD on GitHub

Week Ending February 28, 2021

Developer News

If you contribute to Kubernetes or its subprojects and dependancies, please take The Annual Contributor Survey.

Our infra team is ditching Bazel from Kubernetes core builds. See below for details.

SIG-Node wants your use-case for implementing swap support.

SIG-ContribEx wants to remind you Kubernetes is an inclusive space.

You have until March 9th to submit some GSOC project ideas if your SIG or subproject has potential mentors.

Release Schedule

Next Deadline: Code Freeze, March 9th

Code Freeze is coming! That means it’s time to finish up those PRs for all those enhancements you’ve been working on. 1.21 is just around the corner! The first beta is already out for testing.

Also, the cherry-pick deadline for the next set of patch releases is March 12th.

#99561: Remove Bazel

After months of preparation, the day is finally here! Bazel is being removed as the build system for Kubernetes itself, in favor of the existing make build tooling that releases have always used. While this should be mostly transparent, if you have any PRs in progress that include BUILD changes you will need to fix up your branch. To do this:

  1. Fetch and rebase against upstream.
  2. Run hack/update-bazel.sh during your rebase which will now auto-remove any lingering changes in your PR once the updated script merges in #99561. This script should only take about one second to run.
  3. Carry on as usual.

If you have any questions about the new Bazel-free world, you can ask on k-dev or on Slack. The future is now!

#99163: Implements pod deletion cost

One of the problem with Deployments is that during evictions or terminations, the pod to remove is selected semi-randomly. This can lead to frustration when a better strategy is available with the full picture of the application, for example preferring to scale down on ephemeral cloud instances before longer-lasting ones. Now you can communicate that information down to the controller via a controller.kubernetes.io/pod-deletion-cost: "123" Pod annotation. The string’d numeric value can be any int32 so you can devise whatever numbering scheme your systems require, and apply the annotations from your own controller(s).

#99467: Remove KubeDescribe from SIGDescribe calls

To streamline the tracking of e2e tests, SIG-Testing is requiring all tests be owned by a specific SIG. Additionally some new restrictions to ensure each test is unambiguously owned by only one SIG will be put in place, the bulk of which is fixed up by this PR. If you are responsible for one of the remaining unowned tests, please work with SIG-Testing to get it labelled appropriately.

Other Merges



Version Updates

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.