The Kubernetes project operates by GitOps as much as possible, so our Slack configuration and channel management happens in GitHub, too. Need a new channel, or to change owners or topics for an existing channel? Submit a PR to kubernetes/community. The tools that automate this are in slack-infra, so if you like Slackops and Gitops: contributors wanted.
Next Deadline: Enhancements Freeze, April 30th
The Release Team is fully staffed and Claire posted the schedule, so 1.15 is now fully underway. This means that the Enhancements team have been collecting features and KEPs. By April 30th, your feature or modification needs to be in the enhancements repo, likely with an attached KEP.
1.15.alpha1 came out last week, and release notes collection starts this week.
1.12.8 is expected out this week.
Due to issues with cross-talk between personal forks of
k/k and GitHub’s “helpful” close-issue-via-commit-message integration, we’ve now set up a Prow plugin to block at-mentions and those GitHub keywords from commit log messages. They are still allowed and encouraged in Issues/PRs, just not the commit messages themselves. The Prow plugin will explain all this again if you run afoul of its watchful gaze, but something to keep in mind.
An implementation of the Watch Bookmark KEP, this PR sets up a heartbeat system inside API watches which should allow for both faster resumption on reconnects as well as lower server load. As anyone with a large fleet of custom controllers reconnecting at once knows, this is going to help a lot.
While the PR is relatively small, it gives us this lovely image to show the PR process in a nutshell:
kubectl can-inow warns users when they request an object out of scope
nodeipamhas been cut, since nobody was using it
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.