Google has today announced, that its Kubernetes-powered Container Engine platform which helps in managing containers over its cloud platform, has hit Beta, just in time for DockerCon. Along with that, Google also announced the general availability of Container Registry, its repository to store and distribute container images.

Google earlier developed Kubernetes, the very powerful and robust open source orchestration system for Docker containers, based on Google’s experience in engineering its internal systems. Now Kubernetes powers Container Engine. With Container Engine, you can focus on your application, rather than managing a compute cluster or manually scheduling your containers.

Container Engine supports the common Docker container format. And with Google Container Registry, Cloud Platform makes it a breeze to store and access your private Docker images. And since Container Engine is still in Beta, you can expect a lot of improvements in existing features over time.

With Container Engine,  Google has greatly improved the overall operation-ability and has made it even more efficient.Spin up a managed container cluster of virtual machines, ready for deployment. Your cluster is equipped with capabilities, such as cloud logging and container health checking, to make application management easier.

You can also declare your containers’ requirements, such as the amount of CPU/memory to reserve, number of replicas, and keepalive policy, in a simple JSON config file. The rest of the scheduling will be automatically declared by the container engine.

Upon coming out of Beta, Developers will be charged $0.15 per hour by Google, for running a standard cluster with up to 100 virtual machines. However, do not that those charges are applicable only for managing the cluster. the virtual machines which run your containers are still payable.

As for Container Registry, it isn’t getting any major upgrades, apart from the fact that you can now store your images in Asia and Europe.


Leave a Reply

Your email address will not be published. Required fields are marked *