Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: Fix link to gen_vpc_ip_limits.go #1955

Merged
merged 1 commit into from
Sep 5, 2024
Merged

docs: Fix link to gen_vpc_ip_limits.go #1955

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion doc/development.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down