Cloud Native Networking for Containers in AWS using CNI Plugins - Anirudh Aithal
summary
AWS CNI plugins implement an ENI-per-pod model that gives each task or pod a routable VPC IP by attaching an elastic network interface on demand, eliminating overlay hops and restoring native VPC features like security groups and VPC flow logs. Plugins are written in Go static binaries, packaged as containers, expose CNI add/delete verbs, use a pre-warmed ENI daemon to avoid pod startup latency, hit EC2 ENI attachment limits (and routing table entry limits do not apply), and ship to production (released Oct 2017) with near-100% unit test coverage.
AI-written summary · about
chapters (18)
- 0:00Start
- 1:26Topics covered in today's talk
- 2:13What do applications need?
- 8:38Two listeners : one host
- 10:26Connecting containers across hosts
- 11:21Container communication - 0
- 12:01Container communication - 4
- 12:39How did we do?
- 14:07VPC networking - EC2 instances
- 16:02Packet flow - EC2 instances
- 16:21VPC networking - ENIS
- 18:02VPC networking - containers
- 23:31CNI plugins 101
- 24:04golang or ...?
- 24:55Packaging & distribution
- 25:34Versioning
- 26:14Automating version info
- 26:51Testing the plugin
related talks
16mKeynote: Cloud Native at AWS
37mIntroduction to CNI, the Container Network Interface Project
33mKubernetes Networking: How to Write a CNI Plugin From Scratch
31mEverything You Ever Wanted to Know About CNIs (Container Network Interface) and ...
40mModular Overlay Networking Solutions with the Container Network Interface
29mContainer Networking in Cloud Foundry
34mLow Latency Multi-cluster Kubernetes Networking in AWS
40mCloud, Kubernetes, and Service Networking - Taming the Turtles