Clean up pods
See original GitHub issueI’ve noticed we’re starting to accumulate a whole load of pods which are in the Terminated: Completed
state.
Ideally these should be cleaned up in the same way JupyterHub cleans up pods after the user has logged off.
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
kubernetes cleanup of pods,service,deployment etc
Pods (that were created directly), deployments, and services can all be deleted independently of one another, order doesn't matter. If you want ...
Read more >Garbage Collection - Kubernetes
Garbage collection is a collective term for the various mechanisms Kubernetes uses to clean up cluster resources. This allows the clean up ......
Read more >How to automatically clean up failed Kubernetes Pod every 24 ...
This script is a Kubernetes cronjob which automatically deletes all the pods which are in failed state for more than an 24 hours....
Read more >Clean Up Spark Driver Pods | Fusion 5.7
Spark driver pods are cleaned up using a Kubernetes cron job that runs every 15 minutes. This cron job is created automatically when...
Read more >Clean up - OpenShift Tips
You can also skip the interactivity confirmation using the -f parameter: sudo podman system prune -a -f Deleted Pods Deleted Containers Deleted ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ah, I didn’t realize that this was necessary. It imagine that there are probably a few ways to do this:
On Wed, Mar 14, 2018 at 5:44 AM, Jacob Tomlinson notifications@github.com wrote:
I’m going to close this out now as completed pods are cleaned up when a new cluster is started. There isn’t much we can do about fixing this when clusters are unexpectedly killed.