AWS may be scared of Kubernetes as it becomes the industry standard for managing containers. Why? The open-source platform gives companies a way to run apps across different clouds not just on AWS. Matt Asay over at Tech Republic provides the details.
Matt argues that AWS is so worried, it’s building a dedicated Kubernetes service to meet the threat, although Amazon refused to confirm or deny reports. Industry insiders say AWS doesn’t like Kubernetes because it doesn’t own it. But Matt’s not buying it. AWS builds lots of services on open source projects it doesn’t own.
AWS’s own ECS services is nowhere near as popular as Kubernetes so it makes sense for AWS to invest more in the Google-backed platform. Indeed, CoreOS CEO and Kubernetes contributor Alex Polvi told Matt, "I wouldn't be surprised to see AWS release a Kubernetes-as-a-Service" offering as "customers are asking for it. Look closely and you'll see AWS in the Kubernetes community already. Amazon doesn't like to waste time on open-source development."
The thing about Kubernetes is that it doesn’t just make it easier to move workloads from AWS to another cloud service (e.g. Google Cloud). It also makes it easy to set up containers anywhere, including local machines. Ocado uses Kubernetes to run demanding workloads on their own modest PCs instead of high-powered servers. Mike Bryant, Ocado's network systems team leader, explains: "Most people run Kubernetes on high-performance servers, we run it on PCs - it's a very dramatic cost saving. And it's not just the servers, we don't need enterprise network cabling, we don't need high-end networking kit, we save on cooling - we're really cutting costs."
Matt concludes by stressing that if AWS is to meet the threat it needs to not only offer Kubernetes as a hosted option but provide deep integration by getting AWS engineers to contribute to Kubernetes and influence its future direction.