Last checked and updated on 06 Jun 2026
What Is New in Kubernetes 1.5
Kubernetes 1.5 delivers a massive expansion of stateful application support and introduces powerful new primitives for cluster federation. This release brings core infrastructure to production maturity while expanding into new workloads.
| Category | Key Highlights |
|---|---|
| New Features | StatefulSets (beta), Federated Deployments (alpha), Container Runtime Interface (CRI) alpha implementation, Windows Server Container support (alpha) |
| Improvements | Enhanced node stability, Simplified cluster deployment, Expanded role-based access control (RBAC), Improved federation control plane |
| API Changes | Deployment and DaemonSet API versions promoted to apps/v1beta1, PodSecurityPolicy API promoted to extensions/v1beta1 |
| Deprecations | PetSet renamed to StatefulSet, kube-dns deployment restructuring |
How does StatefulSet improve running stateful applications?
StatefulSets (beta) replace PetSets to provide stable identity and ordered deployment for stateful workloads. Each pod gets a persistent hostname and dedicated storage that follows it through rescheduling.
This matters because databases and other stateful services require predictable network identifiers and persistent storage. StatefulSets guarantee orderly rollout and termination while maintaining stable network identity through DNS records.
In practice, you can now run Cassandra, etcd, or MySQL clusters with proper peer discovery and persistent volumes that survive pod restarts.
What cluster federation capabilities were added?
Federated Deployments (alpha) enable deploying applications across multiple clusters with centralized management. The federation control plane now supports ConfigMaps and DaemonSets alongside existing ReplicaSets and Services.
This expansion means you can manage application rollout and service discovery across cloud providers and regions from a single control plane. The federation API server handles synchronization while preserving cluster autonomy.
How does Container Runtime Interface change container management?
CRI introduces a plugin architecture for container runtimes, starting with an alpha implementation. This gRPC API allows alternative runtimes like containerd and frakti to integrate with kubelet without modifying core Kubernetes.
In practice, this begins the decoupling of Kubernetes from Docker-specific implementations. The CRI shim handles translation between Kubernetes pod specs and runtime-specific container operations.
What Windows Server support is available?
Alpha support for Windows Server Containers enables running Windows-based workloads alongside Linux containers in mixed clusters. This initial implementation covers basic pod, service, and networking functionality.
While still experimental, this opens Kubernetes to .NET Framework applications and other Windows-specific workloads. The support requires Windows Server 2016 and operates through a separate kubelet implementation.
How were node stability and deployment improved?
Numerous node reliability fixes address memory management, container cleanup, and resource reporting. Kubelet now handles disk pressure more effectively and provides more accurate resource accounting.
Cluster deployment simplifies with kubeadm moving to beta, offering a standardized way to bootstrap TLS-enabled clusters. This reduces the complexity of setting up production-grade clusters from scratch.
FAQ
Should I migrate my PetSets to StatefulSets immediately?
Yes, PetSet is deprecated and completely replaced by StatefulSet. The migration is straightforward since StatefulSet maintains the same API patterns and functionality with improved stability.
Is CRI production-ready in 1.5?
No, CRI is alpha and primarily for development and testing. The Docker integration remains the stable production runtime, but CRI lays groundwork for future runtime flexibility.
Can I run Windows containers in production with 1.5?
Not recommended - Windows Server Container support is alpha quality and lacks many features available for Linux containers. Use it only for evaluation and development purposes.
What happens to my existing Deployments with the API change?
Existing Deployments continue working without modification. The new apps/v1beta1 API is backward compatible, but you should update your manifests to use the new API version.
How stable are Federated Deployments for cross-cluster management?
Federated Deployments are alpha quality and should be used with caution. They work for basic scenarios but lack the full feature set of single-cluster Deployments and may have performance limitations.