-
Notifications
You must be signed in to change notification settings - Fork 253
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
Allow global namespace kill settings #135
Comments
@gjcarneiro I think that's the benefit of this chaos solution giving total control to the victim whether he should be treated as a victim or not. |
Ah, I didn't know about chaoskube. That one sounds like it's closer to what I'd like. Thanks for the tip! kube-monkey seems to me to be too conservative. kube-monkey seems more suited to a production environment, when you think your production can survive pods being killed. But I need a more aggressive pod killer, to really stress out the dev cluster. |
I think your use case is valid. There are work-arounds for you (eg. adding the labels to all deployments under the namespace) but obviously that is not convenient. I'm going to re-open this issue to see if we can support setting labels at the namespace level.
When it comes to enrolling apps into kube-monkey, I agree with you that kube-monkey is too conservative, and this is not by design. I do want to have an 'opt out' mode in kube-monkey where ALL apps are automatically opted in, with specific apps being able to opt themselves out. This is a better set up for a dev environment where you want to require developers to build with kube-monkey in mind. |
An additional problem I found was that "kube-monkey/mtbf" can only be integer and it's days, but I don't want to have to wait days for a pod to get killed. |
I have a comment somewhere about changing that to support times using something like or https://github.com/raintank/dur |
@asobti do we have Opt-Out mode enabled now with kube-monkey?.. do not see it in the docs so just want to confirm. |
@asobti Same question as above, do we have the opt out mode now ? For random pods to be deleted instead of specifc ones please ? |
My app has many many deployments, it would be tedious to have to modify all of them.
Can we instead have some annotations on a namespace. I'd like my dev namespace to just randomly kill pods.
The text was updated successfully, but these errors were encountered: