Kubernetes v1.36: What’s New and What Changed

Kubernetes continues to evolve rapidly, and each release brings improvements in performance, security, scalability, and developer experience. The Kubernetes v1.36 release is no exception.

If you are running production workloads or even experimenting with Kubernetes, understanding what changes in each version is critical. A single deprecated API or behavior change can break your deployment if you are not prepared.

In this guide, we break down Kubernetes v1.36 in simple terms, covering new features, improvements, deprecations, and what you should do before upgrading your cluster.

Why Kubernetes Version Updates Matter

Every Kubernetes release includes:

New features
Performance improvements
Security enhancements
Deprecated or removed APIs

Ignoring updates can lead to:

Compatibility issues
Security vulnerabilities
Deployment failures

Overview of Kubernetes v1.36

Kubernetes v1.36 focuses on:

Better scalability
Improved networking
Enhanced security controls
More stable APIs
Continued shift toward Gateway API

Key New Features in Kubernetes v1.36

1. Improved Resource Management

Kubernetes v1.36 enhances how CPU and memory resources are allocated.

Key improvements:

More accurate resource scheduling
Better handling of burst workloads
Reduced resource fragmentation

This leads to:

Improved performance
Better cost efficiency

2. Enhanced Pod Security

Security continues to be a major focus.

New improvements include:

Stricter default security policies
Better enforcement of Pod Security Standards
Improved isolation between workloads

3. Gateway API Advancements

The Gateway API is becoming the future of Kubernetes networking.

In v1.36:

More stable API versions
Improved routing flexibility
Better integration with service meshes

This is important because:

👉 Traditional Ingress is slowly being replaced

4. Networking Improvements

Networking performance and flexibility have improved:

Better load balancing
Improved network policies
Faster service routing

5. Storage Enhancements

Storage management has improved with:

Better CSI driver support
Improved persistent volume handling
Faster attach/detach operations

API Deprecations and Removals

One of the most important parts of any Kubernetes release is what gets removed.

Common Changes in v1.36

Older beta APIs removed
Deprecated fields no longer supported
Stricter validation rules

Why API Deprecations Matter

If your cluster uses deprecated APIs:

Deployments may fail
Controllers may break
Applications may stop working

How to Check for Deprecated APIs

Run:

kubectl get apiservices

Or use tools like:

kube-no-trouble (kubent)
kubectl deprecations

Performance Improvements

Kubernetes v1.36 brings performance gains in:

Scheduler Efficiency

Better placement decisions.

Controller Performance

Faster reconciliation loops.

Cluster Scalability

Handles more nodes and pods.

Security Enhancements

Security updates include:

Stronger RBAC enforcement
Improved secret handling
Better audit logging

Changes in Default Behavior

Some defaults have changed:

More secure configurations
Stricter validation
Reduced reliance on legacy features

Impact on Existing Clusters

Before upgrading, consider:

Compatibility Check

Ensure apps support new APIs.

Backup Cluster

Always take backups.

Test in Staging

Never upgrade production directly.

Step-by-Step Upgrade Strategy

Step 1: Check Current Version

kubectl version

Step 2: Review Release Notes

Always read official Kubernetes notes.

Step 3: Scan for Deprecated APIs

Use tools to detect issues.

Step 4: Upgrade Control Plane

Depends on cloud provider.

Step 5: Upgrade Worker Nodes

Roll out updates gradually.

Step 6: Validate Applications

Check logs and services.

Common Upgrade Issues

Pods Not Starting

Usually due to deprecated APIs.

Networking Issues

Ingress/Gateway misconfigurations.

Storage Errors

CSI driver compatibility issues.

Best Practices for Kubernetes Upgrades

Upgrade one version at a time
Monitor cluster health
Use staging environment
Automate testing

Real-World Insight

From real-world experience:

Most upgrade failures happen because:

Deprecated APIs were ignored
No staging testing
Lack of rollback plan

FAQs

Is Kubernetes v1.36 stable?

Yes, production-ready.

Should I upgrade immediately?

Test first, then upgrade.

What is biggest change?

Gateway API adoption and security improvements.

Final Thoughts

Kubernetes v1.36 continues the trend of making Kubernetes more secure, scalable, and production-ready. However, with improvements come changes that require careful planning.

If you prepare properly, upgrading to v1.36 can significantly improve your cluster performance and reliability.