Stay up-to-date on Kubernetes development in 15 minutes a week.
The Amsterdam Contributor Summit, to be held March 30th, is now taking session proposals.
Please also fill out the Kubernetes developer survey.
Next Deadline: Enhancements Freeze, Jan 28th
The 1.18 release cycle has begun! Time for SIGs to figure out what they’re likely to have for 1.18. Important dates:
The following patch releases, covering all supported versions, will be coming out tommorrow (Jan 14):
Version 1.14 is now out of support, so maybe look at upgrading.
For the 1.18 release, the team will be experimenting with sorting changes by Kind instead of by SIG, in response to user requests. Sascha Grunert has shared an example of 1.17’s notes sorted that way. If you have objections or concerns about this, comment on the PR before it merges on Thursday.
Several years ago, we set ginko.flakeAttempts to “2” in many e2e tests, even pushing an upstream change to ginko. This effectively allowed each test two tries to pass, as a hacky way to deal with network timeouts and other issues. The setting also has given us an artificial confidence in how reliable a lot of code is.
That ends soon,; it’s already been removed from the release-blocking jobs. This does mean that some of your tests that weren’t considered “flaky” before now will be – fix them.
VolumeBinder
field for the scheduler FrameworkHandler so that it works with volumeskubelet_pleg_last_seen_seconds
metric in case the pod event stream goes awayLast 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.