Kubernetes v1.36: Key Changes You Need to Know
Kubernetes v1.36 is set to arrive at the end of April 2026, and it’s crucial to be aware of the changes that could affect your production environments. With a focus on safety and security, the Kubernetes project is implementing a well-documented deprecation policy. This means that stable APIs can only be deprecated when a newer, stable version is available, and they have a minimum lifetime for each stability level. This structured approach helps you plan migrations effectively and avoid sudden disruptions.
Among the notable changes is the retirement of the externalIPs field in Service specifications. This deprecation means you’ll soon lose a straightforward method to route arbitrary external IPs to your services, with full removal planned for v1.43. Additionally, the gitRepo volume plugin, which has been deprecated since v1.11, will be permanently disabled in v1.36. This change emphasizes the need for alternative volume management strategies. On a positive note, Kubernetes v1.36 introduces SELinux volume mounting improvements, allowing for more efficient label application at mount time, which can enhance security posture.
In production, these changes require proactive planning. Make sure to audit your existing configurations for deprecated features like externalIPs and gitRepo. Prepare to transition to supported alternatives well before the removal dates to avoid service disruptions. The deprecation policy helps, but it’s on you to stay ahead of these changes and adapt your architecture accordingly.
Key takeaways
- →Understand the deprecation policy to manage API changes effectively.
- →Prepare for the removal of the externalIPs field by exploring alternative routing options.
- →Transition away from the gitRepo volume plugin as it will be permanently disabled.
- →Leverage the new SELinux volume mounting improvements for better security.
- →Stay informed about version updates to avoid unexpected disruptions.
Why it matters
These changes can significantly impact how you manage network routing and volume configurations in Kubernetes. Failing to adapt could lead to service outages or security vulnerabilities in your applications.
When NOT to use this
The official docs don't call out specific anti-patterns here. Use your judgment based on your scale and requirements.
Want the complete reference?
Read official docsIndustry-standard certifications built by the people behind Linux and Kubernetes. Earn the CKA — the gold standard Kubernetes administrator cert. OpsCanary readers get 30% off year-round with code OPSCANARY3.
Get CKA certified →CiliumCon Returns: Scaling eBPF Networking at KubeCon 2026
CiliumCon is back, and it's crucial for anyone involved in Kubernetes networking. With Cilium as the de facto CNI, understanding its eBPF foundation is key to managing workloads at scale. Don't miss out on the insights that could elevate your cloud-native architecture.
OVHcloud Joins CNCF: What This Means for Kubernetes in Europe
The CNCF's new partnership with OVHcloud marks a significant shift for Kubernetes in Europe. With OVHcloud operating thousands of production Kubernetes clusters using Cilium, this collaboration promises enhanced networking and security for multi-tenant environments.
Migrating to ALB: Mastering oauth2-proxy in Kubernetes
Switching from NGINX Ingress to ALB can be tricky, especially when handling oauth2-proxy. Learn how to configure oauth2-proxy to work seamlessly with ALB's OIDC authentication capabilities.
Get the daily digest
One email. 5 articles. Every morning.
No spam. Unsubscribe anytime.