Happy Pi(e) Day!
The Community Meeting is this Thursday at 1700 UTC/10:00PDT. Join us!
It’s been one year since we changed the release cadence for Kubernetes from 3 months to 4 months. Which means it’s time to survey how you feel about that. Please let us know! Is 3 releases a year better?
We’ve started a further discussion around what it would take to improve Kubernetes reliability.
Do you need to survey the Kubernetes community for your SIG or WG? Contact SIG-ContribEx on Slack or file a survey request issue. We can help you design and promote your community survey, and we have the official SurveyMonkey account.
Speaking of surveys, a Florida University student wants to find out how you feel about our Github bots.
Next Deadline: Exceptions Due, March 21st
We are now in the final week for any Enhancement Exceptions you might need; otherwise the list of what’s being included and what’s being bounced is pretty final. 68 tracked enhancements, plus 25 that have been removed from 1.24. Code Freeze comes on March 29th.
TestGrid does not look good anymore. We have six flaky and one failing job in master-blocking. If the release were next week, we’d be delaying it. Please check if your team owns any failing/flaking tests.
Patch updates for all supported versions (1.23, 1.22, and 1.21) are due out this week. Per earlier LWKDs, there’s a lot of backported bug fixes in these.
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.