# Do not use the Boulegueur in production!

**URL:** <https://discuss.kubernetes.io/t/do-not-use-the-boulegueur-in-production/21880>\
**Category:** Ecosystem\
**Created:** [November 8, 2022, 8:32pm UTC](https://discuss.kubernetes.io/t/do-not-use-the-boulegueur-in-production/21880 "2022-11-08T20:32:08Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jpcarmona](https://avatars.discourse-cdn.com/v4/letter/j/f9ae1b/32.png) [@jpcarmona](https://discuss.kubernetes.io/u/jpcarmona)\
**Post date:** [November 8, 2022, 8:32pm UTC](https://discuss.kubernetes.io/t/do-not-use-the-boulegueur-in-production/21880/1 "2022-11-08T20:32:08Z")

</div>

![screenshot_gameover](https://us1.discourse-cdn.com/flex016/uploads/kubernetes/original/2X/1/17a75acdeb364389cba8f3cd1cf6953fb30e89ea.png)

So I appreciate Kubernetes at work and looove [Unity](https://unity.com/) for side (game) projects.

I got the idea to mix them and I’m proud to present you yet another useless Kubernetes tool called Boulegueur (shaker in Provençal / a dialect from south of France) : as a tank in hostile field, you have to survive and kill opponents.

- Each opponent is a pod in a name space.
- Each kill calls the cluster API to delete the related pod via the Kubernetes API calls.

For now I pompously claim 😛 that it can be used to stress solutions or roughly compare Kubernetes clusters performances.

I’m looking for any other usefulness ideas or a way to enhance solution stress with Kubernetes API calls.

Here are the [install instructions and downloads](https://github.com/jpca/Boulegueur) (binaries for Windows & Mac). Have fun and use it at your own risk 😉

I will appreciate any feedbacks and if someone had fun with it please tell me. For now it was only tested with Rancher desktop / Kubernetes 1.23.6 and a Rancher cluster with Kubernetes 1.18.6.