Kubernetes v1.36 is slated for release at the end of April 2026, bringing a host of enhancements alongside critical deprecations and removals. This version continues the project's commitment to security, stability, and community-driven evolution. While the final list may shift before release, several major developments are already clear: the retirement of the widely-used Ingress NGINX project, the deprecation of the externalIPs field in Services, and reinforced API lifecycle policies. In this article, we break down the five most important changes—and what you need to do to keep your clusters safe and up-to-date. Whether you're a cluster administrator or a developer deploying workloads, understanding these shifts now will save you from disruptions later.
1. Release Timeline and What to Expect
Kubernetes v1.36 is expected to land in late April 2026, following the project's standard three-release-per-year cadence. This cycle is particularly packed with enhancements—both additions and removals. Early summaries indicate improvements in scheduling, security, and API ergonomics. However, the biggest news is the number of features reaching end-of-life. Users should monitor the Kubernetes enhancements tracking sheet and release notes closely. As with every release, alpha and beta features may be added or removed without notice, so teams relying on experimental features need to plan for potential withdrawals. The key takeaway: start preparing your manifests and testing lab now.
2. The Kubernetes API Deprecation Policy in Practice
Kubernetes has a well-defined deprecation policy that dictates how APIs are phased out. Stable APIs can only be deprecated when a newer stable version exists and must remain functional for at least one year after deprecation. Beta APIs must be supported for three releases after being marked deprecated. Alpha APIs can be removed in any release without prior notice. In v1.36, this policy is strictly enforced. A deprecated API still works but emits warnings. Removed APIs are completely unavailable—you must migrate before upgrading. This lifecycle ensures a smooth evolution but demands vigilance. Check the official deprecation guide for each API you use.
3. Ingress NGINX Retirement: What It Means for Your Ingress
On March 24, 2026, SIG Network and the Kubernetes Security Response Committee officially retired the Ingress NGINX project. Effective immediately, no new releases, bug fixes, or security patches will be provided. While existing deployments continue to function and installation artifacts like Helm charts remain available, the lack of ongoing support leaves users exposed to unpatched vulnerabilities. The community is encouraged to evaluate alternative ingress controllers such as NGINX Gateway Fabric, Contour, or Traefik, which align with current security best practices. This retirement is a stark reminder that relying on community-maintained projects carries lifecycle risk. Plan your migration now.
4. Deprecation of .spec.externalIPs in Services
The externalIPs field in the Service spec is being deprecated in v1.36. Historically, this field allowed operators to route arbitrary external IP addresses to Services, often used for bare-metal or hybrid setups. However, it has long been a security headache—misconfiguration can expose internal services to the outside or allow IP spoofing. With deprecation, usage will produce warnings, and the field will be removed in a future release. Migrate by using alternative constructs like externalTrafficPolicy, LoadBalancer Services, or manual endpoint management. The deprecation guide provides detailed steps. Address this early to avoid broken routing after upgrading beyond v1.36.
5. Preparing for Beta and Alpha Removals
Beyond the headline items, v1.36 includes several beta API deprecations and alpha feature withdrawals. Beta APIs that have been deprecated for three releases will be removed—check the list for your commonly used APIs like IngressClass or CSIDriver (if stable versions exist). Alpha features, which can disappear instantly, require special attention. Use the --feature-gates flag carefully and avoid relying on alpha features in production. The Kubernetes community provides migration guides for each removal. Proactively test your configuration against the v1.36 API compatibility matrix. Setting up a CI pipeline that runs against prerelease versions can surface issues early.
Conclusion: Embrace Change with a Plan
Kubernetes v1.36 is not just an incremental update—it's a call to action. The retirement of Ingress NGINX and the deprecation of externalIPs highlight the platform's commitment to security and maintainability. By understanding the API deprecation policy, testing early, and migrating away from deprecated features, you can ensure your clusters remain compliant and resilient. The window of opportunity is narrow: start planning today. Review the official Kubernetes deprecation guide, update your CI/CD pipelines, and engage with your infrastructure team. A smooth upgrade is the result of preparation, not luck.