Stay up-to-date on Kubernetes development in 15 minutes a week.
The Steering Committee Election is still open for voting through Wednesday! Cast your ballot now.
Registration for Kubernetes Contributor Summit Chicago is open.
Next Deadline: Production Readiness Review Freeze, September 28th (this Thursday)
Kubernetes v1.29.0-alpha.1 is live!
Get your KEPs ready for Production Readiness Review. If you’re going to work towards any features, deprecations, or removals during the 1.29 release cycle, please opt-in your KEP(s) before the Enhancements Freeze (October 6th).
This KEP proposes adding NodeExpandSecret
to the CSI Persistent Volume source so that it can be sent by the CSI client as part of the nodeExpandVolume
request to the CSI drivers. CSI spec v1.5 had added an optional secret field to NodeExpandVolumeRequest. The NodeExpandSecret
added by this KEP would support that change. The CSI drivers did not have a method to make use of secretRef
at the time of Node operations such as Node expansion. This is because the subjected CSI request does not carry a secret or credentials in the request. The Kubernetes CSI have implemented a similar mechanism for Controller operations however. secretRef
field is available in the CSI PV source and is making use of it during controllerExpand
request. This KEP adds the same field to the nodeExpandVolume
request.
This KEP was in alpha in the v1.25 release, graduated to beta in v1.27 and is now targeting to graduate to stable in the upcoming v1.29 release. It has been authored by Humble Chirammal.
kubectl --show-events=false
works with PVCsresourcequota.NewMonitor
back where it was; removing it broke stuffTesting updates: RunWatchSemantics, kubeproxy mock framework, WatchSemantics storage
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.