Kubernetes v1.36 is scheduled for release at the end of April 2026, and the development cycle has already revealed significant changes that platform engineers and cluster operators need to understand. This release marks a pivotal moment with the retirement of the widely-used ingress-nginx project alongside numerous API deprecations and feature enhancements.
Whether you’re managing production clusters or planning infrastructure upgrades, understanding what’s coming in v1.36 will help you avoid breaking changes and take advantage of new capabilities. Here’s everything you need to know.
Ingress NGINX Retirement: End of an Era
On March 24, 2026, Kubernetes SIG Network and the Security Response Committee officially retired the ingress-nginx project. This is not merely a deprecation notice—it’s a complete end-of-life for one of the most popular ingress controllers in the Kubernetes ecosystem.
The retirement means:
- No further releases or bug fixes
- No security vulnerability patches
- No community support or maintenance
- Existing deployments continue to function but at increasing risk
This decision prioritizes the safety and security of the broader Kubernetes ecosystem. ingress-nginx had accumulated technical debt and security complexity that couldn’t be reconciled with modern security best practices.
Migration path: Organizations currently using ingress-nginx should evaluate alternatives like NGINX Ingress Controller (NGINX’s commercial offering), Traefik, HAProxy, Istio Gateway, or Envoy Gateway. Each offers different trade-offs in features, performance, and operational complexity.
Understanding the Deprecation and Removal Process
Kubernetes follows a well-defined API deprecation policy that governs how features transition from stable to deprecated to removed:
- Generally Available (GA) APIs may be marked deprecated when a newer stable version exists, but cannot be removed within a major Kubernetes version
- Beta/Pre-release APIs must be supported for 3 releases after deprecation
- Alpha/Experimental APIs may be removed in any release without prior notice
All API removals include migration paths documented in the official deprecation guide. The ingress-nginx retirement follows similar lifecycle discipline, ensuring the ecosystem can evolve without abrupt disruption.
Notable Deprecations and Removals in v1.36
The v1.36 release includes several API and feature deprecations. While the complete list is still evolving, cluster administrators should audit their manifests and controllers for:
- Deprecated API versions scheduled for removal
- Feature gates transitioning from beta to GA or being removed
- Configuration options that have been superseded
Use tools like kubent (kube-no-trouble) or the built-in API deprecation warnings to identify workloads using deprecated APIs before upgrading.
How to Prepare Your Clusters
Migrating away from ingress-nginx and preparing for v1.36 requires a systematic approach:
1. Audit current ingress usage – Identify all ingress resources across your clusters and document which ingress class they’re using. ingress-nginx was commonly the default, so look for ingresses without explicit class annotations.
2. Evaluate replacement ingress controllers – Consider your requirements: Do you need advanced routing features? Are you already running a service mesh? What’s your team’s operational expertise with each option?
3. Test migrations in development – Never migrate production ingress directly. Use staging or development environments to validate your chosen replacement handles your traffic patterns correctly.
4. Update monitoring and alerting – Ingress controller metrics differ between implementations. Update your dashboards and alerts to reflect the new controller’s metric names and dimensions.
The Bottom Line
Kubernetes v1.36 represents a significant, if bittersweet, milestone. The retirement of ingress-nginx removes a widely-used but increasingly problematic component from the ecosystem. While migration requires effort, the long-term security and maintenance benefits justify the work.
Start planning your migration strategy now if you haven’t already. The April release date is approaching quickly, and being proactive will prevent emergency scramble situations.
Sources
- Kubernetes Blog: v1.36 Sneak Peek (March 30, 2026)
- ingress-nginx Retirement Announcement (March 24, 2026)
- Kubernetes Deprecation Policy
- Kubernetes Deprecation Guide