The Steering Committee election closes at 23:59 UTC on November 4th. Cast your ballot as soon as you can.
WG-Reliability has a second draft of their proposal around improving Kubernetes reliability by blocking new features if testgrid is flaky. Please review!
Next Deadline: Feature Blogs, Nov. 2 (Code Freeze, Nov. 16)
Tuesday is the final pre-Code Freeze deadline: it’s time to get your Feature Blog items in. We’re starting the countdown to Code Freeze on the 16th – the Release team has already started semi-weekly burndown meetings.
Up until now, we had two systems sharing a configuration struct: probes and lifecycle hooks. This has lead to some confusing mis-features like HTTP calls for lifecycle hooks. These have now been split from a single
ProbeHandler for probes and
LifecycleHandler for hooks. In keeping with our compatibility guarantees both new structs are currently identical but it opens the door for future improvements, adding features only where it makes sense. If you’re building a PodSpec in Go code anywhere and it includes probes or hooks, make sure you update your struct names to match the new API.
While the venerable
kubectl get events has long served for basic debugging and shell scripting, there was always a lot of room for improvement. As a new alpha-level command, we have
kubectl alpha events to build this future on. The biggest new feature is a
--for CLI option which takes an object reference and filters the output. Check out the KEP for ideas on future features which I’m sure SIG-CLI would love help with!
PodSecurity has seen a huge burst of activity, so let’s just go through all of them!
restrictedpolicy will reject/warn
kubectl -ohas autocomplete, and autocomplete makes more helpful suggestions
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.