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.

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

k8s: update eni-max-pods #2079

Merged
merged 1 commit into from
Apr 18, 2022
Merged

Conversation

jpculp
Copy link
Member

@jpculp jpculp commented Apr 18, 2022

Description of changes:

Updates eni-max-pods with mappings of new instance types to their maximum number of pods supported.

Taken from: https://github.com/awslabs/amazon-eks-ami/blob/aed6c88d7783464edb443d3e1c796ddce2a30375/files/eni-max-pods.txt

Testing done:

Build AMI, launched c6a.xlarge instance and verified that the host comes up fine and joins my cluster.

[ssm-user@control]$ apiclient exec admin sheltie pluto max-pods
58

Terms of contribution:

By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.

Updates `eni-max-pods` with mappings of new instance types to their maximum number of pods supported.

Taken from https://github.com/awslabs/amazon-eks-ami/blob/aed6c88d7783464edb443d3e1c796ddce2a30375/files/eni-max-pods.txt
Copy link
Contributor

@zmrow zmrow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎤

@jpculp jpculp merged commit 29aa0bd into bottlerocket-os:develop Apr 18, 2022
@jpculp jpculp deleted the eni-max-pods-update branch April 18, 2022 23:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants