5 result(s)
Kubernetes v1.35 (planned 2025-12-17) introduces several deprecations and new/advanced features. Major removals/deprecations include cgroup v1 support removal, deprecation of kube-proxy ipvs mode, and final support for containerd v1.x (users must move to containerd 2.0+). Notable enhancements likely in v1.35 include node declared features (alpha), in-place Pod resource updates (GA), pod certificates (beta), numeric taint comparisons, continued progress on user namespaces, and image volumes becoming default.
This article collects practical Kubernetes configuration best practices: prefer current stable APIs, keep manifests minimal and version-controlled, write YAML carefully (watch boolean values), group related objects, favor controllers (Deployments/Jobs) over naked Pods, use Services and DNS properly, avoid hostNetwork/hostPort unless necessary, apply semantic/common labels, add helpful annotations, and use kubectl features like applying directories, label selectors and server-side apply to simplify management.
Kubernetes SIG Network and the Security Response Committee announced the retirement of Ingress NGINX. Best-effort maintenance will continue until March 2026; after that there will be no further releases, bug fixes, or security updates. Users are advised to migrate to Gateway API or another Ingress controller.
The 2025 Kubernetes Steering Committee election concluded. Four of seven seats were up for election; the incoming members begin two-year terms immediately. The post announces the newly elected members, continuing members, election officers, emeritus members, and gives ways for the community to follow and participate in Steering Committee work.
Gateway API v1.4.0 (released Oct 6, 2025) advances Kubernetes service networking with three features promoted to Standard (BackendTLSPolicy, supportedFeatures in GatewayClass status, and named rule fields for Routes) and several experimental additions (Mesh/XMesh, default Gateways, and an ExternalAuth filter for HTTPRoute). The release also adds per-port TLS/client-certificate configuration to address connection coalescing security, introduces a couple of breaking validation changes, improves CI/docs, and is usable on Kubernetes >=1.26.