fix: duplicate --max-pods arguments in KUBELET_EXTRA_ARGS #8533
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes #7946 by preventing duplicate
--max-podsarguments inKUBELET_EXTRA_ARGSwhen using the deprecatedMaxPodsPerNodesetting with AL2 managed nodegroups.Problem
When
MaxPodsPerNodeis set, eksctl'smakeMaxPodsScriptfunction appends--max-podstoKUBELET_EXTRA_ARGSwithout checking if it already exists, resulting in:Solution
Modified
makeMaxPodsScriptto:--max-pods=<number>arguments using sed--max-podsvalueImpact
--max-podsissueTesting
The fix ensures only one
--max-podsargument appears inKUBELET_EXTRA_ARGS, with eksctl'sMaxPodsPerNodevalue taking precedence.