🎉 Locust Kubernetes Operator v1.0.0 is here! 🎉

This release marks a major milestone for the operator, bringing in a key change for enhanced security and usability, alongside other improvements.

💥 Breaking Change 💥

• ClusterRole Enabled by Default: To streamline setup and ensure the operator has the necessary permissions out-of-the-box, the clusterRole is now enabled by default (k8s.clusterRole.enabled: true). If you were previously relying on this being disabled, please update your configurations accordingly. This change helps in automatically managing cluster-wide resources without manual intervention.

🚀 Features & Improvements 🚀

• Fine-Grained Resource Management: We've introduced more granular control over resource requests and limits for both the load generation pods and the metrics exporter. This allows for better resource allocation and stability of your load testing environments.
• Enhanced Stability: Various under-the-hood improvements have been made to increase the operator's stability and reliability.
• Documentation Revamp: The official documentation has been overhauled to make it more comprehensive, user-friendly, and easier to navigate. Whether you're a new user or a seasoned pro, you'll find valuable information to get the most out of the operator.

🙌 Upgrading 🙌

When upgrading to v1.0.0, please be mindful of the clusterRole change. We recommend reviewing your values.yaml file to ensure a smooth transition.

A huge thank you to all our contributors for making this moment possible!

📋 Full Changelog: locust-k8s-operator-0.11.0...locust-k8s-operator-1.0.0