---
title: "EKS-ellent news for the Kubernetes community"
source: "https://www.tigera.io/blog/eks-ellent-news-for-the-kubernetes-community-6f9d23273ae5/"
description: "Amazon Web Services Elastic Container Service for Kubernetes (EKS) will support networking with Calico, an open source project managed by Tigera."
---

[Company Blog](https://www.tigera.io/category/company-blog/)

[Technical Blog](https://www.tigera.io/category/technical-blog/)

# EKS-ellent news for the Kubernetes community

By [Andrew Randall](https://www.tigera.io/blog/author/andrewrandall/) on Nov 29, 2017 • 2 min read

By now, you’ve probably already heard — at AWS re:invent this morning, AWS CEO Andy Jassy announced Elastic Container Service for Kubernetes (EKS). While some may dismiss this as Amazon being the last to the party, by dint of their dominance in the public cloud space this is important news. This is particularly exciting for Tigera as we have been working with the AWS folks over the past few months to enable secure application connectivity for EKS workloads. Given that perspective, I would also like to share some thoughts on what lies ahead.

For many in the open source community around Kubernetes, the introduction of EKS, while much-anticipated, will be a source of trepidation. Amazon’s reputation (perhaps well earned in the past) is for aggressively monetizing open source projects without giving back to the community. However, there are signs that EKS might be different.

For starters, Amazon stepped up to the plate as Platinum members of the Cloud Native Computing Foundation (CNCF). This followed the hiring of industry luminary Adrian Cockroft (one of the founders of the ‘cloud native’ movement at Netflix) who has been highly vocal in setting a more open direction within AWS.

We have also seen that one of the primary drivers for organizations adopting Kubernetes is the ability to design multi-cloud application architectures. We have been collaborating in the field with AWS and some large customers on such use cases, where there is a hard requirement for Kubernetes-in-AWS to operate identically to their on-premise deployment. Of course they will always want to make services available that differentiate AWS — but they are committing to EKS being a 100% upstream Kubernetes experience.

It is also encouraging how AWS is approaching the development of EKS with partners in the community. For example, working with Heptio on identity integration and with Tigera on container network interface (CNI) and network policy — with the resultant code being open sourced and upstreamed wherever possible.

The bottom line is that this marks a watershed moment in the evolution of cloud and the maturity of Kubernetes. The container wars are over, the community is the winner, and Tigera is excited to be partnering with AWS to help realize their vision for Kubernetes as part of a truly open ecosystem.

[Open Source](https://www.tigera.io/tags/open-source/)[Partner/Integration](https://www.tigera.io/tags/partner-integration/)[Announcements](https://www.tigera.io/tags/announcements/)

## Related posts

[![EU Cyber Resilience Act: Europe Just Put Your AI Agents on a 24-Hour Clock](https://www.tigera.io/app/uploads/2026/10/EU-Cyber-Resilience-Act-AI-Agents-featured.png)](https://www.tigera.io/blog/eu-cyber-resilience-act-europe-just-put-your-ai-agents-on-a-24-hour-clock/)

#### [EU Cyber Resilience Act: Europe Just Put Your AI Agents on a 24-Hour Clock](https://www.tigera.io/blog/eu-cyber-resilience-act-europe-just-put-your-ai-agents-on-a-24-hour-clock/)

By [Alister Baroi](https://www.tigera.io/blog/author/alister-baroi/)
on Oct 5, 2026

In short, the EU Cyber Resilience Act (CRA) puts binding cybersecurity requirements on any software sold as a product in the EU, and it does not carve out AI agents. Since 11th September 2026, any...

[Read more](https://www.tigera.io/blog/eu-cyber-resilience-act-europe-just-put-your-ai-agents-on-a-24-hour-clock/)

[![Meet Mylo: An AI-native way to work with Calico](https://www.tigera.io/app/uploads/2026/09/Meet-Mylo-An-AI-native-way-to-work-with-Calico.png)](https://www.tigera.io/blog/meet-mylo-an-ai-native-way-to-work-with-calico/)

#### [Meet Mylo: An AI-native way to work with Calico](https://www.tigera.io/blog/meet-mylo-an-ai-native-way-to-work-with-calico/)

By [Phil DiCorpo](https://www.tigera.io/blog/author/phil-dicorpo/)
on Sep 3, 2026

A library of Calico tools and skills — delivered through the Calico MCP Server What if your hardest network question took ten minutes instead of ten days? Anyone who has operated Kubernetes networking at scale...

[Read more](https://www.tigera.io/blog/meet-mylo-an-ai-native-way-to-work-with-calico/)

[![Why We Built Lynx: Bringing Control to the Age of AI Agents](https://www.tigera.io/app/uploads/2026/06/Introducing-Lynx-NEW-TEMPLATE-2026-Tigera-brand.png)](https://www.tigera.io/blog/why-we-built-lynx-bringing-control-to-the-age-of-ai-agents/)

[Featured Blog](https://www.tigera.io/category/featured-blog/)

#### [Why We Built Lynx: Bringing Control to the Age of AI Agents](https://www.tigera.io/blog/why-we-built-lynx-bringing-control-to-the-age-of-ai-agents/)

By [Ratan Tipirneni](https://www.tigera.io/blog/author/ratan/)
on Jun 17, 2026

For a decade, one idea has guided everything we’ve built at Tigera: How do you secure a dynamic system with a lot of moving parts that is changing rapidly, with a programmatic approach? Calico has...

[Read more](https://www.tigera.io/blog/why-we-built-lynx-bringing-control-to-the-age-of-ai-agents/)

<!-- plugin=object-cache-pro client=phpredis metric#hits=6155 metric#misses=17 metric#hit-ratio=99.7 metric#bytes=2214244 metric#prefetches=0 metric#store-reads=409 metric#store-writes=13 metric#store-hits=423 metric#store-misses=6 metric#sql-queries=31 metric#ms-total=977.17 metric#ms-cache=56.18 metric#ms-cache-avg=0.1335 metric#ms-cache-ratio=5.8 -->
