Skip to content
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

Integrated Locust load testing #20531

Draft
wants to merge 2 commits into
base: parent-helm-charts
Choose a base branch
from

Conversation

RachalCassity
Copy link
Member

@RachalCassity RachalCassity commented Jan 29, 2025

Note: Delete the description statements, complete each step. None are optional, but can be justified as to why they cannot be completed as written. Provide known gaps to testing that may raise the risk of merging to production.

Summary

Locust will be used for automated load testing. A Locust script is mounted to the Locust master deployment and worker deployment and deployed to EKS. The Locust command --master -f /locustfile.py is used to run Locust in master mode while specifying the location of the locustfile in the ConfigMap. The worker deployment may not be needed in the future. Load test can be initiated in the Locust UI.

image

Potential Modifications if this fails:

  1. Add host to class APIUser method. We do not want to use staging-api.va.gov.
    class APIUser(HttpUser): abstract = True task_set = VetsApiClient min_wait = 0 max_wait = 1000 host = 'https://staging-api.va.gov' # Will need domain for VetsNext Cluster

Related issue(s)

  • department-of-veterans-affairs/issues/74651

@RachalCassity RachalCassity marked this pull request as draft January 30, 2025 17:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

EKS Upgrade Testing Plan: Step 10: Load Testing
1 participant