Kubernetes v1.36 "Haru" Released: Calico v3.32 Brings Full Support
🔄 Update — 16. June 2026: v1.37 Development Cycle and v1.33 End of Support
The development cycle for Kubernetes v1.37 has officially commenced, with the Enhancements Freeze going into effect today, 16 June 2026. In parallel, administrators must prepare for the upcoming end of support for v1.33, while KubeCon India 2026 is set to bring new insights to the cloud-native ecosystem.
What’s new?
- Feature Freeze for v1.37: Today’s Enhancements Freeze (AoE) for Kubernetes v1.37 defines the scope of new features and Kubernetes Enhancement Proposals (KEPs) for the next release, following the release of the first alpha version (
v1.37.0-alpha.1) on 10 June. - End of Support for Version 1.33: Kubernetes v1.33 will reach its official End of Support (EOS) date on 28 June 2026, highlighting the urgency for cluster administrators to keep their environments updated.
- KubeCon India 2026: KubeCon + CloudNativeCon India 2026 is scheduled for 18–19 June, focusing heavily on AI infrastructure and platform engineering running on Kubernetes.
Why this adds to the article
While the original article discusses the stability and compatibility of Kubernetes v1.36 and Calico v3.32, this update highlights the continuous lifecycle of container orchestration platforms, requiring proactive upgrades as older versions retire and v1.37 takes shape.
🔄 Update — 13. June 2026: Kubernetes Management and AKS Pricing in Focus
Recent developments in the Kubernetes ecosystem focus on simplifying cluster management and introducing new integration features. Alongside updated pricing structures for Azure Kubernetes Service (AKS), current discussions highlight improved developer workflows through VS Code integration and Azure Arc.
What’s new?
- Simplified Management: RedMonk’s analysis “Kubernetes Without the Chaos” highlights new approaches for organizations to reduce the operational complexity of Kubernetes infrastructures.
- AKS Pricing Updates: Microsoft has updated the pricing details for Azure Kubernetes Service (AKS), directly impacting cost planning for cloud-native projects.
- Hybrid Cloud Integration: Expanded documentation for Azure Arc-enabled Kubernetes and the VS Code Kubernetes extension streamlines the management of hybrid clusters directly from the developer environment.
Why this adds to the article
While the main article discusses the release of Kubernetes v1.36 and CNI compatibility (Calico v3.32), this update shows how cloud providers and communities are leveraging the new platform stability to simplify day-to-day management and optimize operational costs.
Summary
Tigera has announced the release of Calico Open Source v3.32, which is fully compatible with the newly released Kubernetes v1.36, codenamed “Haru”. This update ensures that Calico users can immediately benefit from the latest Kubernetes features while receiving enhanced networking and security capabilities.
What happened?
Coinciding with the release of Kubernetes v1.36 “Haru”, Tigera released Calico v3.32. This new version of Calico has been specifically validated to work seamlessly with the changes in K8s 1.36. Kubernetes v1.36, under the name “Haru” (Japanese for spring), introduces various improvements in scalability and API stability.
Why it matters
Compatibility between the container orchestration system (Kubernetes) and the network plug-in (CNI - Calico) is crucial for the stability of cloud-native infrastructures. Rapid updates like Tigera’s minimize downtime and allow organizations to implement Kubernetes security updates without delay from third-party tools.
Evidence
Tigera confirmed compatibility in their official blog and published the release notes for Calico v3.32 on GitHub. The timely delivery highlights the close collaboration between the Calico project and the Kubernetes community.
Analysis
The codename “Haru” suggests a phase of renewal and stability. Calico v3.32 focuses on efficiently utilizing the new API features of K8s 1.36. There are particular synergies in the areas of NetworkPolicies and performance in large clusters that are leveraged by this coordinated release.
Practical Takeaways
- Administrators should ensure Calico is updated to v3.32 before upgrading to K8s 1.36.
- Support for older Kubernetes versions remains, but the latest features are only fully exploited in the 1.36/3.32 combination.
- Test the upgrade in a staging environment first to rule out specific incompatibilities with custom network policies.
Open Questions
- What specific performance benchmarks result from the combination of K8s 1.36 and Calico v3.32?
- Are there breaking changes in the Kubernetes API v1.36 that require adjustments to existing Calico configurations?
Sources
- Calico networking for Kubernetes - Tigera.io
- Releases · projectcalico/calico - GitHub
- Kubernetes support in Visual Studio Code
- Overview of Azure Arc-enabled Kubernetes
- Kubernetes Without the Chaos - RedMonk
- Azure Kubernetes Service (AKS) Pricing
- Kubernetes v1.37 Release Cycle - kubernetes.dev
- KubeCon + CloudNativeCon India 2026 - linuxfoundation.org