-
Notifications
You must be signed in to change notification settings - Fork 121
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] Kill only pods which do have more then 1 sibling replica #469
Comments
Good idea. I think that could be added fairly easily here: chaoskube/chaoskube/chaoskube.go Line 531 in d1b517d
if len(pods) <= 1 {
continue
} But we would need to write a test case to confirm that. |
Hi 👋, created the PR for this. Would appreciate the feedback! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We're using chaoskube to kill random pods and also to "balance" our cluster.
We have many microservices that are running with more then one replica however we have a few services that can only run with 1 replica. Our monitoring checks the health of the pods by calling their web endpoint and notify us if the service is down.
It would be nice if chaoskube can be configured to only kill pods that belong to a deploymen/ReplicaSet with more then one other pod. I couldn't find any way to configure that.
As a workaround for now we're going to set a label for that pods to prevent them from being killed.
The text was updated successfully, but these errors were encountered: