Kubernetes v1.36 Deprecations and API Lifecycle: Your Questions Answered

Kubernetes v1.36 is slated for release at the end of April 2026, introducing important API removals and deprecations as part of the project's lifecycle management. This Q&A covers the deprecation policy, key changes like the retirement of Ingress NGINX and the deprecation of .spec.externalIPs in Services, and practical steps to prepare for migration. For more details, jump to the deprecation policy, Ingress NGINX retirement, or externalIPs deprecation.

How does Kubernetes handle API deprecation and removal?

Kubernetes follows a strict deprecation policy to ensure stability. Stable (GA) APIs can only be deprecated when a newer stable version of the same API is available, and they must remain functional for at least one year after deprecation. During that period, usage triggers a warning. Beta APIs must be supported for at least three releases after deprecation, while alpha APIs may be removed in any release without notice. All removals comply with this policy, and migration options are documented in the deprecation guide.

Why was Ingress NGINX retired, and what should users do?

On March 24, 2026, SIG-Security and the Security Response Committee retired the Ingress NGINX project to prioritize ecosystem safety. No further releases, bugfixes, or security updates are provided. While existing deployments continue to function and artifacts like Helm charts remain available, users are strongly encouraged to evaluate alternative ingress controllers that meet current security and maintenance practices. This retirement reflects Kubernetes' lifecycle discipline, ensuring gradual evolution without abrupt disruption.

What is being deprecated in v1.36 regarding Service externalIPs?

The .spec.externalIPs field in Service objects is being deprecated in v1.36. This field allowed quick routing of arbitrary external IPs to Services, but it has been identified as a known security headache due to potential misconfiguration or abuse. Deprecation means it will continue working for now with a warning, but users should plan to migrate to more secure alternatives. The exact replacement options will be detailed in the deprecation guide.

How do stable, beta, and alpha APIs differ in deprecation timelines?

Stable APIs have the longest lifecycle: they may be deprecated only when a newer stable version exists, and they must remain available for at least one year. Beta APIs must be supported for three releases after deprecation. Alpha APIs, being experimental, have no minimum support period and can be removed in any release without prior notice. This tiered approach balances stability for production users with the flexibility to iterate quickly on new features.

Where can I find migration guidance for deprecated APIs?

Whenever an API is removed, the Kubernetes project communicates migration options in the official deprecation guide. For v1.36, the guide will include specific advice for transitioning away from .spec.externalIPs and for replacing Ingress NGINX. Users should regularly consult the guide and test upgrades in non-production environments to ensure a smooth transition. The project's strong commitment to lifecycle discipline means deprecations are well-documented and phased over time.