What does HackerNews think of amazon-vpc-cni-k8s?

> 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

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.

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