Stay up-to-date on Kubernetes development in 15 minutes a week.
You have one day (or less) left to vote for Steering Committee members.
The call for presentations for the Maintainer Summit in Kubecon India is now open. The Maintainer summit combines a Kubernetes Contributor Summit with contributor discussions and presentations by other CNCF projects.
Next Deadline: Production Readiness, October 3
It’s the second week of 1.32 and hopefully you’re hard at work on your planned Enhancements.
Currently resource allocation in PodSpec is done at the container level. The scheduler aggregates the resources requested by all the containers to find a suitable Node for the Pod. The Pod API lacks a way to specify limits at the Pod level, limiting the flexibility and ease of resource management for Pods as a whole. This KEP extends the Pod API with a resource spec at the Pod level. This new feature can be used to complement the existing resource limits and make things easier for tightly coupled applications. The KEP explains how the resource limits will be applied in different cases when Pod level and container level requests and limits are specified, as well as how the OOM score calculation will be done.
This KEP is tracked for alpha stage in the upcoming v1.32 release.
scheduler_perf tests, supporting multi-namespacekubeadm join/reset handles etcd members only if their URLs/IDs are unique or existcupy instead of CUDA samplesUnstructured.GetManagedFields function by eliminating unnecessary deep copying of JSON valueNodeUnschedulable pluginresolvConf in drop-in kubelet config filesNodeUnschedulable, podtopologyspread & NodeResourcesFit in requeueing scenariosQuantity.AsApproximateFloat64resourceupdates.Update channel to prevent blocking during device plugin data transmission to kubeletnodeAffinityspec.terminationGracePeriodSeconds should not be overwritten by MaxPodGracePeriodSecondsLast 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.