Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature request] Support for Locust Lib ConfigMap #226

Open
jgrevich opened this issue Dec 6, 2024 · 1 comment
Open

[Feature request] Support for Locust Lib ConfigMap #226

jgrevich opened this issue Dec 6, 2024 · 1 comment
Labels
Feature request Something should be improved

Comments

@jgrevich
Copy link

jgrevich commented Dec 6, 2024

Is your feature request related to a problem? Please describe.
We currently use the locust helm chart to manage our locust cluster. Our locust tests require the support of a lib directory. It appears the only way to use this k8s operator requires changes to our test files or patching the locust image used, neither of which is ideal.

Describe the solution you'd like
The locust helm chart has a locust_lib_configmap value, which allows users like us to include our lib directory in a ConfigMap. Is something like that possible with the operator?

Describe alternatives you've considered
We can modify our locust tests so they do not require a lib directory, or we could patch the locust image used by the operator.

@AbdelrhmanHamouda
Copy link
Owner

Hello @jgrevich,
Thank you for taking the time to open this ticket!

Based on your explanation of the feature i don't see any blockers from adding this feature to the operator. that being said, as this is a holiday season, I will be able to look into this Jan 2025. If this is urgent or someone in your team have the technical knowhow to contribute to the operator, i'm more than happy to work with you to get it done and shipped faster.

@AbdelrhmanHamouda AbdelrhmanHamouda added the Feature request Something should be improved label Dec 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature request Something should be improved
Projects
None yet
Development

No branches or pull requests

2 participants