Add Cleaner instance to find unhealthy deployments #46
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A Deployment is defined unhealthy if all of its Pods have more than 50 restarts (i.e, each of its Pods have at least one container with restartCount greater than 50). Any such a Deployment instance is scaled down (i.e, spec.replicas is set to zero).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This cleaner identifies and removes unhealthy Deployments in your Kubernetes cluster based on pod restarts.
Unhealthy: A Deployment is considered unhealthy if all its Pods have each container restarted at least 50 times.
Action: When an unhealthy Deployment is found, it will be automatically scaled down to zero replicas (effectively removing it).
Fixes #45