Google's Container Engine For Running Docker Containers On Its Cloud Platform Is Now Generally Available
Frederic Lardinois / TechCrunch :
Context & Ripple Effects
Container Engine's general availability completes a build-out Google started earlier in 2015, when it launched private Docker repositories for Cloud Platform users and brought Windows Server to Compute Engine — the pieces needed to make its cloud usable for both Linux-native container shops and traditional Windows workloads. The move also puts Google in direct competition with CoreOS, whose Kubernetes-based Tectonic platform reached general availability that November.
First-order effects
- Cloud Platform customers can now run managed Docker container clusters instead of assembling their own orchestration on raw Compute Engine VMs.
- CoreOS loses its position as one of the few production-ready ways to run Kubernetes-backed container infrastructure commercially.
Second-order effects
- Microsoft answers within months by taking its own Azure Container Service to general availability, making managed container hosting a two-cloud race rather than a Google differentiator.
- Google's private Docker registry becomes the default storage tier for Container Engine users, deepening lock-in across the Cloud Platform stack.
Third-order effects
- If the pattern holds, container orchestration stops being a product and becomes a commodity feature every major cloud ships — which is effectively what happened, as Google later renamed the offering Kubernetes Engine and added formal release channels and Windows Server container support.
The trend: Cloud platforms are shifting from selling virtual machines to competing on managed container orchestration as the default way workloads get deployed.