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

Recommended way to set ENABLE_PREFIX_DELEGATION #2155

Closed
soostdijck opened this issue Jul 8, 2022 · 4 comments
Closed

Recommended way to set ENABLE_PREFIX_DELEGATION #2155

soostdijck opened this issue Jul 8, 2022 · 4 comments

Comments

@soostdijck
Copy link

Description

The amount of pods per node is limited by the vpc cni addon, but there is a feature to increase the limit to something useful by setting "ENABLE_PREFIX_DELEGATION" and "WARM_PREFIX_TARGET" in the EKS cluster.

What is the recommended way to do this? I see other EKS modules that simply fire up a kubectl and set the settings, but that isn't very elegant (plus local-exec won't work using TFcloud).

info

More info can be found in this blog article

@bryantbiggs
Copy link
Member

Unfortunately, that is the current method for enabling this functionality. You can refer to the example I provided here that demonstrates how to achieve this in Terraform

@bryantbiggs
Copy link
Member

closing for now since its outside the scope of this module

@mohag
Copy link

mohag commented Oct 26, 2022

Description

The amount of pods per node is limited by the vpc cni addon, but there is a feature to increase the limit to something useful by setting "ENABLE_PREFIX_DELEGATION" and "WARM_PREFIX_TARGET" in the EKS cluster.

What is the recommended way to do this? I see other EKS modules that simply fire up a kubectl and set the settings, but that isn't very elegant (plus local-exec won't work using TFcloud).

There seems to be a 3rd-party provider that makes it nicer...

(A 3rd-party provider is not ideal though)

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants