What’s changing in Kubernetes v1.36?

Removals like gitRepo volumes, deprecation of Service externalIPs, Ingress NGINX retirement, plus GA SELinux labelling.

Do I need to migrate from gitRepo in Kubernetes?

Yes, now—it's disabled in v1.36. Use init containers or git-sync.

Is Kubernetes v1.36 safe for production?

After migrations, yes. But audit deprecations first.

Kubernetes v1.36: The Security Axe Falls on Old Habits

Kubernetes v1.36 isn't just another update—it's a cleanup crew evicting risky relics. But are these 'enhancements' forcing you into pricier cloud lock-in?

Open Source Beat Apr 07, 2026 4 min read

Kubernetes v1.36 release graphic with deprecation warnings and security locks

⚡ Key Takeaways

Major removals: gitRepo gone, externalIPs deprecated, Ingress NGINX retired. 𝕏
Security drives changes, but migrations benefit cloud vendors most. 𝕏
SELinux volume labelling GA for faster Pod starts on enforcing systems. 𝕏

Published by

Open Source Beat

Community-driven. Code-first.

#Kubernetes v1.36 #SELinux #SELinux enhancements #deprecations #gitRepo removal #security enhancements

Worth sharing?

Get the best Open Source stories of the week in your inbox — no noise, no spam.

Originally reported by Kubernetes Blog

⚡ Key Takeaways

The 60-Second TL;DR

Open Source Beat

Share this article

Worth sharing?

Related Stories

Kubernetes Just Killed Ingress NGINX: Half Your Clusters Are Suddenly Vulnerable

BunkerM Implants Local AI Brains into MQTT Brokers

Kubernetes Hits 82% in Production – AI Scales on It, But Culture Stalls Everyone Else

Ingress2Gateway 1.0: Kubernetes' Smooth Escape from Ingress Doom

Stay in the loop