<p>A company would like to scale their microservice application using namespaces, namespace represents a separate application per each client. The application consists of 22 microservices, the company has 80 clients, hence there will be 22 * 80 = 1760 pods in the cluster. The diagram is given below.</p>
<p>It was initially calculated that it would be enough to have 4 r4.xlarge nodes to keep proper performance. But the company has encountered a different kind of problem: <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html#AvailableIpPerENI" rel="nofollow noreferrer">the number of IP addresses</a> per instance. For example, for 4 nodes of r4.xlarge type only: 4(nodes) * 4(network interfaces) * 15(Private IPv4 addresses) = 240 addresses available, but 1760 needed!</p>
<p>Increasing the number of nodes several times over budget.
Are there any ways to avoid that IPs amount limitation? Or maybe you can propose another solution<a href="https://i.stack.imgur.com/UJK37.jpg" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/UJK37.jpg" alt="enter image description here" /></a></p>

GutsOut
<p>This is something we intend to solve with an upcoming new version of the VPC CNI plugin. There is work being done to increase the number of VPC IP addresses available to pods on any given worker node. You can track this roadmap item <a href="https://github.com/aws/containers-roadmap/issues/138" rel="nofollow noreferrer">here</a>.</p>
