amazon-vpc-cni-k8s

I believe you're correct, although pedantically that would only apply if one is using their vpc-cni <https://github.com/aws/amazon-vpc-cni-k8s#readme> and not with a competing CNI. Kubelet offers a configurable for the number of Pods per Node <https://github.com/kubernetes/kubelet/blob/v0.26.2/config/v1...> which defaults to 110 for what I would presume is CIDR or pid cgroups reasons and thus is unlikely to differ by instance size as the ENI limit you mention does (IIRC)

Well an overlay network by definition is always going to be transparent to you. But no the AWS VPC CNI does not create an overlay. It's just layer 3. It works by adding ENIs to your worker nodes with secondary IP addresses on them. And those secondary IPs are from your VPC's address space. See: https://github.com/aws/amazon-vpc-cni-k8s/blob/master/docs/c...

> Turns out internal IP addresses are a resource, too. That's not what is happening in AWS. IP address are resources (duh), but that's no the issue. With their CNI plugin each pod gets its own Elastic Network Interface. ENIs aren't just virtio's virtual network, it could be ENA (100Gbps) or Intel VF (10Gbs). It's a hardware limitation of amazon virtualization stack starting with previous generation instances. > I was quite surprised when pods stopped scheduling even though CPU and memory were available. This is well documented here: https://github.com/aws/amazon-vpc-cni-k8s

AWS was sending "ACTION REQUIRED" email to all EKS users about this. The Github issue is: https://github.com/aws/amazon-vpc-cni-k8s/issues/641

Amazon's EKS is still in preview. I wouldn't expect it to be generally available (that is, stable) for several months at least. I've also heard reports that getting into the preview is really difficult at the moment. It's using a new networking model: https://github.com/aws/amazon-vpc-cni-k8s > Alpha This is an experimental release as part of the Amazon EKS Preview. Interfaces and functionality may change. Expect bugs (and please help us squash them). DO NOT use for production workloads.

But if you follow the link the under the "components" section of your link you will see the link to the project proposal: https://github.com/aws/amazon-vpc-cni-k8s/blob/master/propos... There they clearly state: >"To run Kubernetes over AWS VPC, we would like to reach following additional goals: Networking for Pods must support high throughput and availability, low latency and minimal jitter comparable to the characteristics a user would get from EC2 networking"

How does it compare to AWS' own CNI plugin? https://github.com/aws/amazon-vpc-cni-k8s

They announced they were going to be using their open source cni plugin https://github.com/aws/amazon-vpc-cni-k8s/