search

kubernauts / jmeter-kubernetes

Load testing as a service (LTaaS) with Apache Jmeter on kubernetes
Apache License 2.0
362 stars 249 forks source link

Change jmeter_slaves_deploy.yaml from Deployment to DaemonSet #25

Closed brentchang closed 4 years ago

brentchang commented 4 years ago

As the document described[1] the jmeter-slave replicas should be the same number with Kubernetes node.

However, when our team used jmeter-slave deployment, we found that sometimes more than one jmeter-slave pods were deployed on the same node, which led to not enough CPU resources on that node.

After our internal discussion, we found that the DaemonSet should be more suitable for the jmeter-slave pods.

Also update the jmeter_stop.sh permission that can be executed (chmod +x).

[1]https://blog.kubernauts.io/load-testing-as-a-service-with-jmeter-on-kubernetes-fc5288bb0c8b

infinitydon commented 4 years ago

@brentchang - Thanks for this.. I will suggest that we make the case of using a DS optional since not everyone will want to have jmeter PODs on all their nodes..

brentchang commented 4 years ago

@infinitydon Thanks for your suggestion. yes in our case we all use dedicated GKE clusters to do the Load tests.

To your standpoint, I think you're right, not everyone wants DS.