Last checked and updated on 05 Jun 2026
What Is New in Kubernetes 1.3
Kubernetes 1.3 delivers major enhancements in scalability, user experience, and application support. This release bridges the gap between development and production with features designed for larger, more complex workloads.
| Category | Key Highlights |
|---|---|
| New Features | Cross-cluster Federation, Minion -> Node rename, PetSets (alpha), rkt container engine support, Multiple schedulers |
| Improvements | Cluster scaling (2000 nodes), Performance optimizations, Simplified deployment (kube-up), Enhanced UI |
| Core Updates | Updated to Docker 1.11, Support for OpenStack, CloudProvider integration |
| Beta & Alpha | Init Containers (beta), Deployments (beta), Autoscaling (beta), AppArmor annotations (alpha) |
How does Federation work in Kubernetes 1.3?
The new Federation feature (alpha) allows you to manage multiple Kubernetes clusters as a single logical entity. You can create a federated service that automatically deploys and maintains itself across all clusters in your federation, providing a global VIP and DNS record.
In practice, this means you can achieve cross-zone or cross-region high availability without manual intervention. A service update gets propagated to all clusters, and the federation layer handles the complexity of distributing the workload and aggregating API resources.
What are PetSets for stateful applications?
PetSets (alpha) provide the primitive needed to run stateful distributed systems like etcd, Zookeeper, or databases on Kubernetes. They guarantee unique, persistent identities and stable hostnames for each pod in the set, which is critical for applications that require stable network identities or persistent storage.
This matters because prior to PetSets, running stateful apps was a manual and fragile process. PetSets bring ordered deployment, scaling, and graceful termination to pods that need to be treated as individual, unique "pets" rather than interchangeable "cattle."
Why was 'Minion' renamed to 'Node'?
The term "Minion" was officially replaced with "Node" throughout the codebase and documentation. This change was made to adopt a more standard and widely understood terminology within the infrastructure community.
For developers, this means all API references, command-line tool outputs, and logs now use Node. While the functionality is identical, scripts or tools parsing older terminology will need to be updated to avoid breakage.
What performance and scale improvements were made?
Kubernetes 1.3 significantly raises the bar for cluster size, officially supporting clusters up to 2000 nodes. This is achieved through core optimizations in the API server, controller manager, and scheduler to reduce latency and CPU usage.
Key improvements include better caching, more efficient watch operations, and general reductions in API server load. For large-scale deployments, this translates to faster pod scheduling and more responsive cluster management operations.
What's new for application deployment and management?
Deployments graduated to Beta, offering a declarative way to manage rolled updates and rollbacks for Pods and ReplicaSets. Init Containers also moved to Beta, providing a reliable way to run setup scripts before the main app containers start.
Furthermore, Horizontal Pod Autoscaling is now in Beta, allowing you to automatically scale the number of pods in a replication controller based on observed CPU utilization. These features collectively provide a much stronger foundation for managing application lifecycles in production.
FAQ
Is the Federation feature production-ready?
No, the Cross-cluster Federation capability is released as an alpha feature in 1.3. It is intended for experimentation and testing rather than production workloads, as the API may change in future releases.
Can I use PetSets for my database?
Yes, but with caution. PetSets are an alpha feature, making them suitable for experimentation but not for mission-critical production databases yet. Ensure you have robust backup and recovery procedures for any data stored on persistent volumes.
Do I have to rewrite my scripts that use 'minion'?
Yes, the rename from 'Minion' to 'Node' is a breaking change. Any scripts, tools, or documentation that reference the old term (e.g., in kubectl output or API calls) will need to be updated to use 'Node' to work correctly with Kubernetes 1.3.
What is the benefit of supporting rkt alongside Docker?
Adding rkt as a container runtime option provides users with flexibility and choice. It allows organizations to select a container engine based on their specific requirements for security, operational workflow, or compatibility.
How does the new UI improve upon the previous one?
The updated dashboard UI offers a more comprehensive and user-friendly overview of your cluster. It provides better visualization of resources, simplified navigation, and more detailed information about workloads, making day-to-day cluster management significantly easier.