Quick View: AWS & Kubernetes (K8s) Report

AWS KubernetesToday The Information published a story that “Amazon (AWS) Considering New Cloud Service to Combat Google.” The Information highlighted that Kubernetes was created by Google. However, The Information missed stating that while Google is the biggest contributor to it today (Red Hat is second), Kubernetes was open-sourced and is hosted by the Cloud Native Computing Foundation (CNCF) now and not Google.

The Information’s article speculates that Amazon is considering an AWS Kubernetes managed service to compete with Google and other public cloud providers.

Kubernetes has become a de facto standard for container scheduling and management. For those new to containers check out this primer I wrote back in May as to the importance of the container developer standard.

In addition to the fast adoption of Kubernetes, and Docker, by software developers, the public cloud players have been making moves to increase their support of it. Microsoft purchased Deis, and subsequently committed to “continue our contributions to Workflow, Helm, and Steward and look forward to maintaining our deep engagement with the Kubernetes community.”

IBM also provided a managed Kubernetes offering that “removes the distractions related to managing your clusters, and extends the power of your apps with Watson and other cloud services, binding them with Kubernetes Secrets.”

Cloud City Ventures Quick View On AWS Kubernetes Managed Service

The Cloud City Ventures quick view on this is that AWS is constantly evaluating the market. The fact that AWS is studying Kubernetes should not be a surprise to public cloud analysts or experienced users considering that Google Cloud, Microsoft Azure and IBM all have a Kubernetes market position.

While AWS may be looking at lots of potential projects, adopting a Kubernetes managed services (similar to Google’s GKE) might signal to enterprise customers that AWS’s EC2 Container Service (ECS) will have internal competition with this new potential offering. AWS would have to split development resources across both ECS and a managed Kubernetes offering. If AWS offered both, clients on the AWS platform would be confronted by two similar offerings. Clients would benefit significantly from a native Kubernetes managed service as AWS clients looking to deploy Kubernetes on AWS today must do it themselves on EC2.

I have reached out to AWS’s container team for a comment and will update the article if I receive a reply.

 

Matthew Scott