Week Ending April 28, 2024

Developer News

We have two new Working Groups, built around the needs of new workloads like AI/ML:

• WG Device Management will develop tooling and infrastructure to help users add accelerators and other specialized hardware to their Kubernetes clusters
• WG Serving will enable AI/ML inference workloads that are not batch-oriented (as a complement to WG Batch)

SIG-Docs is having almost total leadership turnover with old leaders stepping down, new ones stepping up, and some folks swapping roles.

SIG-Architecture has published new guidance for when a feature can skip Alpha release.

Reminder: SIG Annual Reports are due by May 1. It’s mostly automated now, so please get it done. Any contributor to the SIG can work on the report, not just the Leads.

Release Schedule

Next Deadline: v1.31 cycle starts, May 13th, 2024

We’re in the period between releases. Shadow applications for the v1.31 release team are open until May 15. The tentative dates for the v1.31 cycle are from May 13th to August 15th, 2024.

KEP of the Week

4138: Pod Conditions for Starting and Completion of Sandbox Creation

The KEP adds a pod condition called PodReadyToStartContainers. It shows pod readiness to start containers immediately after pod sandbox creation. It provides a clear indication to cluster administrators when the initialization phase of successfully scheduled pods is completed. Existing conditions such as PodScheduled and Initialized do not adequately convey this specific phase of pod lifecycle. With this Enhancement, users can monitor and analyze pod sandbox creation latency metrics. This can assist in setting Service Level Objectives (SLOs) and can be used by custom controllers and operators to optimize reconciliation strategies for sandbox creation failures.

This KEP is tracked to promote to beta in the v1.30 release.

Other Merges

• Validate common name formats in CEL
• client-go’s REST client gets WatchList access
• Prevent a race condition in the transforming informer, including resync; backported
• --hostname-override works correctly with external cloud providers
• Add a function to check etcd supported features
• Reorganize kube-proxy metrics (“and stuff”), giving nftables mode its own metrics
• kubeadm: remember to download the config during upgrade, use output/v1alpha3 for printing
• Remove cloudprovider code from volume managers
• Kubemark supports burst and qps tests
• New metrics: not-really-invalid packets
• Contextual logging: component-helpers
• Test Cleanup: TrafficDistribution, watch cache

Deprecated

• remove deprecated output.kubeadm.k8s.io/v1alpha2 API
• enable-client-cert-rotation is the new experimental-cert-rotation
• remove deprecated DefaultHostNetworkHostPortsInPodTemplates feature gate
• Remove pre-1.20 checkpoint support from DeviceManager

Version Updates

• sigs.k8s.io/yaml to 1.4.0
• cri-tools to 1.30.0
• cel-go to 0.20.1, changes optional to optional_type

Subprojects and Dependency Updates

• Kernel Module Management 2.1.0: GC delay, reorder kmod loading.
• kubernetes-sig/kubebuilder v3.14.1: Upgrades to controller runtime, bug fixes.
• kubernetes/kompose v1.33.0: Ability to select stage in multistage dockerfile, labels for initContainers, networkmode service.
• kubernetes/cloud-provider-openstack openstack-cinder-csi-2.29.1.
• etcd-io/etcd v3.4.32: Fix to LeaseTimeToLive returning error, updates to compaction log.
• containerd/containerd v1.7.16: HPC port forwarding, updates to HTTP fallback to better account for TLS timeout.
• cri-o/crio-o: Update pinned images list on config reload, keep track of exec calls for container.
• grpc/grpc v1.63.0: API to inject connected endpoints into servers, upgrades to Protobuf.

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.