[AWS/EKS] Tune VPC CNI warm pool for kubernetes_node_scale in EksKarpenterCluster#6557
Open
kiryl-filatau wants to merge 19 commits intoGoogleCloudPlatform:masterfrom
Open
[AWS/EKS] Tune VPC CNI warm pool for kubernetes_node_scale in EksKarpenterCluster#6557kiryl-filatau wants to merge 19 commits intoGoogleCloudPlatform:masterfrom
kiryl-filatau wants to merge 19 commits intoGoogleCloudPlatform:masterfrom
Conversation
…ded and matched case-insensitively
…, quieter node_scale logs output
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
NOTE: should be merged only after PR#6512 is merged.
What
In
EksKarpenterCluster._PostCreate, when the benchmark iskubernetes_node_scale, tune the VPC CNI warm-pool settings on theaws-nodeDaemonSet inkube-systemand wait for the rollout tocomplete before the benchmark run starts.
Settings applied:
Why
At large node counts (5k) the default CNI warm-pool behaviour
aggressively pre-allocates ENIs and secondary IPs, consuming EC2 IP
capacity before pods are scheduled. Reducing the warm targets lowers
per-node IP pre-allocation, which reduces InsufficientCapacityError
and FailedScheduling pressure during scale-up.
Scope
The tuning block is guarded by
'kubernetes_node_scale' in FLAGS.benchmarks, so it is a no-op for all other benchmarks. Noexisting behaviour is changed outside that gate.
Testing
Validated with two back-to-back 5k-node runs on EKS + Karpenter in
us-east-1. Both runs completed with status
SUCCEEDED.