Enable kubernetes_node_scale benchmark (up to 5k nodes) on AWS EKS with Karpenter#6512
Draft
kiryl-filatau wants to merge 19 commits intoGoogleCloudPlatform:masterfrom
Draft
Enable kubernetes_node_scale benchmark (up to 5k nodes) on AWS EKS with Karpenter#6512kiryl-filatau wants to merge 19 commits intoGoogleCloudPlatform:masterfrom
kiryl-filatau wants to merge 19 commits intoGoogleCloudPlatform:masterfrom
Conversation
…' and 'GetNodeNames' methods
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
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.
Summary
Enables running the
kubernetes_node_scalebenchmark (0→5k→0→5k nodes) on AWS EKS with Karpenter. The benchmark scales a deployment with pod anti-affinity, measures scale-up/scale-down and a second scale-up, then tears down the cluster.Main changes
t, higher CPU limit), EKS/Karpenter cluster lifecycle and cleanup._CleanupKarpenter— retry with backoff on AWS throttle (RequestLimitExceeded), treat “ENI not found” as success; usessuppress_failurefor these cases.get nodespass in_StopWatchingForNodeChanges; resolve machine type only for current nodes, use"unknown"for others to avoid thousands of kubectl calls on 5k-node runs.NOTE: Hardcoded values to be updated