-
Notifications
You must be signed in to change notification settings - Fork 106
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
Add scale tests #916
base: main
Are you sure you want to change the base?
Add scale tests #916
Conversation
… operator-scale to use the module
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.
Looking good from the first pass. Appreciate your hard work on this!
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.
Looking good. Add some questions/comments for your consideration.
Thanks!
@@ -180,9 +193,23 @@ func TestMain(m *testing.M) { | |||
os.Exit(1) | |||
} | |||
|
|||
var providerFile string | |||
if isScaleTest { | |||
providerFile = "eks.tf" |
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.
For the future, we might move the scale testing TF to its own directory, then we could just copy over the TF from it into the target TF working directory. That would allow is to extend the TF for a specific cluster target. Not a blocker.
This PR allows for testing a number of concurrently installed VDS, VSS and VPS CRs. You can specify the number by type with the env vars:
VDS_CREATE_COUNT
,VSS_CREATE_COUNT
, andVPS_CREATE_COUNT
. You can further specify different combos, such asVSS_KVV1_CREATE
,VSS_KVV2_CREATE
,VSS_BOTH_CREATE
, etc..If none specified, the default count will be used (previous behavior).
Prereq: Doormat AWS sandbox account
Before running any make commands, make sure to log in into doormat and export the AWS keys:
doormat login && eval $(doormat aws -a <AWS ACCOUNT NAME> export)
Make sure to export the path to your vault license:
export TF_VAR_vault_license_path=<path to license file>
make -f scale-testing.mk create-eks
make -f scale-testing.mk deploy-workload
make -f scale-testing.mk scale-tests