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.

Sign up for GitHub

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

docs (#2188): Add Locust Kubernetes Operator #2288

Merged
merged 1 commit into from
Jan 16, 2023
Merged

docs (#2188): Add Locust Kubernetes Operator #2288

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 14 additions & 3 deletions docs/running-in-docker.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,10 +39,21 @@ official Locust docker image as a base image::


Running a distributed load test on Kubernetes
=============================================
==============================================

The easiest way to run Locust on Kubernetes is to use a `Helm chart <https://helm.sh/>`_.
HELM
*****

One of the ways to run Locust on Kubernetes is to use a `Helm chart <https://helm.sh/>`_.
Copy link
Contributor Author

@AbdelrhmanHamouda AbdelrhmanHamouda Jan 16, 2023 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This rephrasing of the statement is purely an opinion and I fully understand if Locust want to state that HELM is the easiest way to run distributed tests. If the rephrasing is not okay, please let me know and I will restore the original phrasing.

Opinion justification:
HELM is an incredible tool and the provided chart does a lot to make sure that the processes is easy. However, the user is not really "shielded" from Kubernetes and have to be exposed and aware of many other moving peaces (e.g. deployments, configmaps, etc...) in order to get things right. That in my opinion makes it so the term "easiest" may cause a bit of misguidance.


There is a good helm chart here: `github.com/deliveryhero/helm-charts <https://github.com/deliveryhero/helm-charts/tree/master/stable/locust>`_.

Note: this Helm chart is a separate project, and not supported by Locust maintainers.
Note: this Helm chart is a separate project, and not supported by Locust maintainers.

Kubernetes Operator
*******************
Another way to run Locust on Kubernetes is to use the `Locust Kubernetes Operator <https://abdelrhmanhamouda.github.io/locust-k8s-operator/>`_.

The Locust Operator is designed to unlock easy, seamless & effortless distributed performance testing in the cloud.

Note: the Locust Kubernetes Operator is a separate project and is not supported by Locust maintainers.