-
Notifications
You must be signed in to change notification settings - Fork 163
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
kube-janitor in production clusters #1913
Comments
SGTM, we should just make sure that it does not do "more than it should" and that the additional API requests do not cause impact. |
Does it support select by namespace? |
The first action item should be to create e2e test for janitor @hjacobs |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please consider deploying kube-janitor to production clusters.
We have an locust based load test, that we sometimes temporarily deploy to perform load tests. We have a separate one to ensure SLOs are being met that terminates but this one is deployed with the web interface to try out different configurations.
Due to misconfiguration of the deployment pipeline, it got accidentally deployed due to a dependency update and ran in production for some time until discovered by accident. Given the resources requested, this was quite a bit of money wasted. We've fixed the configuration of the pipeline but I would feel even more comfortable only having this around temporarily via kube-janitor.
The text was updated successfully, but these errors were encountered: