-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Comments
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 |
closing for now since its outside the scope of this module |
There seems to be a 3rd-party provider that makes it nicer... (A 3rd-party provider is not ideal though) |
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. |
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
The text was updated successfully, but these errors were encountered: