Following Amazon’s many announcements at AWS re:Invent last month, including its new Amazon Elastic Container Service for Kubernetes (EKS), many wondered how Amazon is going to position itself within the Kubernetes community, and how its EKS and full-service Fargate managed container offering will impact the Amazon Elastic Container Service (ECS) and the Kubernetes community as a whole.
Developers noticed that Fargate almost negates the need for EKS, which raised questions with our guests on the latest episode of The New Stack Analysts, where we were joined by Matt Asay, Adobe’s head of developer ecosystems at Adobe, and Krishnan Subramanian, who is the founder and chief research advisor, for infrastructure, application platforms and DevOps for Rishidot Research.
The question is, why offer EKS when ECS is doing so well? The answer, Asay went on to explain, is simple: “Why not offer that service? If it wins over ECS, great. They’re in that game. If it doesn’t, and ECS continues to grow, maybe not overtly marginalize Kubernetes, but effectively marginalize Kubernetes.”
Subramanian also touched on the fact earlier in the discussion that, “When Amazon has the lead, they go with their opinionated approach, it’s my way or the highway. When they’re behind, they offer choice, offer options to the customers.”
In This Edition:
1:52: The announcement of AWS supporting Kubernetes as a service in its EKS offering.
7:20: Aurora serverless—What is the positioning there with Kubernetes?
17:56: Of the different open source serverless platforms, which looks the most promising?
21:44: AWS’s participation in the Kubernetes community.
25:13: Community and code investment in open source, and whether Amazon will spend the time and resources to do the same with AWS.
25:51: Cultural shift.
Feature image: AWS CTO Werner Vogels speaking at this year’s Re:Invent