-
Notifications
You must be signed in to change notification settings - Fork 813
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create EBS CSI Driver scale-test tool #2292
Create EBS CSI Driver scale-test tool #2292
Conversation
Code Coverage DiffThis PR does not change the code coverage |
hack/ebs-scale-test/helpers/cluster-setup/scale-cluster-config.yaml
Outdated
Show resolved
Hide resolved
49cbf49
to
4ae77bb
Compare
4ae77bb
to
94c9338
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
94c9338
to
2502c6d
Compare
2502c6d
to
3acb83d
Compare
/lgtm |
/retest Flake: |
/approve Ran through scale tests locally and confirmed they run as intended send metrics and logs to S3 and clean up all resources when done.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ElijahQuinones The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind documentation
What is this PR about? / Why do we need it?
Validate that the EBS CSI Driver is capable of managing volumes at the scale of your largest EKS clusters with our
scale-test
tool. See/hack/ebs-scale-test/README.md
for more info.Karpenter cluster-type, more scalability test-types, and more scalability test observability features coming soon.
Scope of this PR: One-step run pre-allocated scale-sts scalability tests.
Running
./scale-test create && ./scale-test run && ./scale-test clean
with no extra environment variables set will:How was this change tested?
Revision 2 edit: Ran through scale-test create, run, and clean loop again. Also manually tested extra features, the results of which I included in the review comments of those features. Thanks.
Please follow the README.md to run these scale tests yourself.
Timing:
Cluster Setup: ~18 min
Run: ~8 min for 1000 replica test
Cluster Cleanup: ~10 min
Does this PR introduce a user-facing change?