You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enable the VPC CNI addon to support the CNI tuning plugin, allowing for more granular sysctl customization.
Use Case
Our current on-premises cluster employs the tuning plugin to modify specific system parameters (sysctls) at the cluster level. These adjustments, such as:
are necessary to align the cluster's default behavior with our specific operational requirements.
Proposed Solution
I propose adding a new tuning plugin configuration block analogous to the one used for disabling IPv6. This would allow users to specify an array of sysctl key-value pairs, which would then be automatically converted into another tuning plugin configuration block, enabling flexible customization.
Other Information
No response
Acknowledgements
I may be able to implement this feature request
CDK version used
2.147.3
EKS Blueprints Version
1.15.1
Node.js Version
v20.13.0
Environment details (OS name and version, etc.)
Linux
The text was updated successfully, but these errors were encountered:
Describe the feature
Enable the VPC CNI addon to support the CNI tuning plugin, allowing for more granular sysctl customization.
Use Case
Our current on-premises cluster employs the tuning plugin to modify specific system parameters (sysctls) at the cluster level. These adjustments, such as:
are necessary to align the cluster's default behavior with our specific operational requirements.
Proposed Solution
I propose adding a new tuning plugin configuration block analogous to the one used for disabling IPv6. This would allow users to specify an array of sysctl key-value pairs, which would then be automatically converted into another tuning plugin configuration block, enabling flexible customization.
Other Information
No response
Acknowledgements
CDK version used
2.147.3
EKS Blueprints Version
1.15.1
Node.js Version
v20.13.0
Environment details (OS name and version, etc.)
Linux
The text was updated successfully, but these errors were encountered: