How does it work⚓

To run a performance test, basic configuration is provided through a simple and intuitive kubernetes custom resource. Once deployed the Operator does all the heavy work of creating and scheduling the resources while making sure that all created load generation pods can effectively communicate with each other.

To handle the challenge of delivering test script/s from local environment to the cluster and in turn to the deployed locust pods, the Operator support dynamic volume mounting from a configMaps source. This is indicated by a simple optional configuration. Meaning, if the configuration is present, the volume is mounted, and if it is not, no volume is mounted.

Since a "Picture Is Worth a Thousand Words", here is a gif! Short demo for how the operator works

Steps performed in demo⚓

Test configmap created in cluster.
LocustTest CR deployed into the cluster.
The Operator creating, configuring and scheduling test resources on CR creation event.
The Operator cleaning up test resources after test CR has been removed event.