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

Docs reference to Locust k8s Operator removed without apparent reasoning #2790

Closed
2 tasks done
AbdelrhmanHamouda opened this issue Jul 4, 2024 · 5 comments
Closed
2 tasks done
Labels
bug stale Issue had no activity. Might still be worth fixing, but dont expect someone else to fix it

Comments

@AbdelrhmanHamouda
Copy link
Contributor

Prerequisites

Description

Hello,
The docs reference to the Locust k8s Operator has been removed in this commit without an apparent reasoning.

I assume it's a bug (hence this issue). If this is indeed intended, I would like to know what was the policy change resulting to this and how we can have the project listed again. Also since the docs still point to the "third party" helm chart in another section.

The project in my opinion offers a tremendous value for people wanting to run locust on k8s.

Command line

N/A

Locustfile contents

N/A

Python version

N/A

Locust version

latest

Operating system

N/A

@cyberw
Copy link
Collaborator

cyberw commented Jul 4, 2024

Hi! I moved it to https://github.com/locustio/locust/wiki/Extensions, because I wanted to group external things (except for the ones I actually maintain) there, but forgot to add a link. I do want to keep/reintroduce some of best things in the main docs however (and that includes your operator).

Anyways, we're doing a bit of a documentation refresh and will be sure to put it back in somewhere.

@AbdelrhmanHamouda
Copy link
Contributor Author

Thanks @cyberw for the timely and clear response. I have a better context now and I'm looking forward to seeing the revamped docs!

If you would like, I'm happy to close the issueor we can keep it open for tracking "as you prefer".

@cyberw
Copy link
Collaborator

cyberw commented Jul 4, 2024

We can keep it open for now. If I forget, that way I'll get a reminder when it goes stale :)

Copy link

github-actions bot commented Sep 3, 2024

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 10 days.

@github-actions github-actions bot added the stale Issue had no activity. Might still be worth fixing, but dont expect someone else to fix it label Sep 3, 2024
Copy link

This issue was closed because it has been stalled for 10 days with no activity. This does not necessarily mean that the issue is bad, but it most likely means that nobody is willing to take the time to fix it. If you have found Locust useful, then consider contributing a fix yourself!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug stale Issue had no activity. Might still be worth fixing, but dont expect someone else to fix it
Projects
None yet
Development

No branches or pull requests

2 participants