Add volume lifecycle churn scale test#2880
Open
torredil wants to merge 1 commit intokubernetes-sigs:masterfrom
Open
Add volume lifecycle churn scale test#2880torredil wants to merge 1 commit intokubernetes-sigs:masterfrom
torredil wants to merge 1 commit intokubernetes-sigs:masterfrom
Conversation
Signed-off-by: Eddie Torres <torredil@amazon.com>
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Code Coverage DiffThis PR does not change the code coverage |
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.
What type of PR is this?
ebs-scale-test enhancement.
What is this PR about? / Why do we need it?
Our existing scale tests all follow a sequential pattern where volumes are created, attached, then torn down. That doesn't capture what happens with workloads like Spark pipelines, where volumes are constantly being created and destroyed in overlapping phases.
This PR adds a new test type that models that pattern. It runs waves of short lived jobs, each with its own PVC. When a wave's jobs complete, their resources are deleted and the next wave is immediately submitted so the driver is handling both teardown and provisioning concurrently, which is the behavior we want to benchmark.
Works with both pre-allocated and karpenter cluster types using the existing scale test framework.
How was this change tested?
Does this PR introduce a user-facing change?