docs (#2188): Add Locust Kubernetes Operator #2288
Conversation
locustio#2188 - Update `Running a distributed load test on Kubernetes` docs section to include Locust Kubernetes Operator. - Small reformat of the section to clearly list all possibilities (HELM & Operator) in a structured manner.
| HELM | ||
| ***** | ||
|
|
||
| One of the ways to run Locust on Kubernetes is to use a `Helm chart <https://helm.sh/>`_. |
There was a problem hiding this comment.
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.
|
Hello @cyberw , I attempted to follow the contribution docs as close as i could. Things look good locally. Please let me know if something is missing. Also, I have a proposal to move the "Running in Kubernetes" section to it's own dedicated page. The topic is too big "and irrelevant IMHO" to be under Running in Docker. |
|
Great stuff. Yes, splitting it to a separate page makes sense. |
#2188
Running a distributed load test on Kubernetesdocs section to include Locust Kubernetes Operator.