From aa6a44b7dd58981922b33880889b0bfb9875a949 Mon Sep 17 00:00:00 2001 From: Brett Campbell Date: Thu, 5 Sep 2024 15:47:05 -0700 Subject: [PATCH] docs: Fix link to gen_vpc_ip_limits.go s/main/master/ --- doc/development.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/development.md b/doc/development.md index a7661d4b1..bdbd0427b 100644 --- a/doc/development.md +++ b/doc/development.md @@ -16,7 +16,7 @@ hack/mkdocs.sh serve By default, the maximum number of pods able to be scheduled on a node is based off of the number of ENIs available, which is determined by the instance type. Larger instances generally have more ENIs. The number of ENIs limits how many IPV4 addresses are available on an instance, and we need one IP address -per pod. You can [see this file](https://github.com/aws/amazon-vpc-cni-k8s/blob/main/scripts/gen_vpc_ip_limits.go) +per pod. You can [see this file](https://github.com/aws/amazon-vpc-cni-k8s/blob/master/scripts/gen_vpc_ip_limits.go) for the code that calculates the max pods for more information. As an optimization, the default value for all known instance types are available in a resource file