🚀 Feature Request: Support for On-demand EKS Cluster Provisioning
Description
Currently, klocust is an excellent tool for deploying distributed Locust on Kubernetes. However, it operates under the assumption that an EKS cluster is already up and running with a configured kubeconfig.
I would like to propose a feature that allows klocust to automatically provision an EKS cluster if one does not exist, based on specific conditions or configuration flags.
Proposed Solution
Introduce a mechanism to trigger the EKS cluster creation process during the deployment phase. This could include:
- Conditional Flags: Adding flags like
--create-cluster or --provision-eks.
- Cluster Configuration: Supporting a
cluster-config.yaml to define the cluster specifications (region, instance types, node count, etc.).
Why is this needed?
Seamless Experience: It transforms klocust from a "deployment helper" into a "complete performance testing solution" on AWS.
Lowering the Barrier: New users can start load testing without deep knowledge of manual EKS setup.
CI/CD Efficiency: Simplifies ephemeral testing environments where a cluster is needed only for the duration of the load test.
🚀 Feature Request: Support for On-demand EKS Cluster Provisioning
Description
Currently, klocust is an excellent tool for deploying distributed Locust on Kubernetes. However, it operates under the assumption that an EKS cluster is already up and running with a configured
kubeconfig.I would like to propose a feature that allows klocust to automatically provision an EKS cluster if one does not exist, based on specific conditions or configuration flags.
Proposed Solution
Introduce a mechanism to trigger the EKS cluster creation process during the deployment phase. This could include:
--create-clusteror--provision-eks.cluster-config.yamlto define the cluster specifications (region, instance types, node count, etc.).Why is this needed?
Seamless Experience: It transforms klocust from a "deployment helper" into a "complete performance testing solution" on AWS.
Lowering the Barrier: New users can start load testing without deep knowledge of manual EKS setup.
CI/CD Efficiency: Simplifies ephemeral testing environments where a cluster is needed only for the duration of the load test.