Kubernetes 1.3 tackles current and future container questions

Kubernetes 1.3, the latest major revision of Google’s container cluster management system, debuts today. It’s available as an open source project on GitHub and in Google Cloud Platform’s Container Engine service.

The new features speak to some of the latest issues involving containers today and Google’s long-term plans for a hybrid cloud built with their services.

The united states of Kubernetes

On the face of it, Google can use most of the new features in Kubernetes 1.3 to further boost containers as a service on Google Cloud Platform. According to a draft copy of the blog discussing Kubernetes 1.3, most of the additions were driven by requests from businesses using Kubernetes in production. Among them is a higher number of nodes available in a cluster (it’s now a maximum of 2,000); the ability to deploy services across availability zones, both on-prem and off; and easier support for stateful applications out of the box.

The container world has been looking more toward stateful application support as its fundamentals become established. Containers are immutable by default, but applications within containers depend on state to be useful, and data volume containers aren’t a complete solution.