Issue
On demand runner task containers seem to stay in "Succeed" status and do not auto clean. There ends up being 100's of containers in the Waypoint namespace which makes it hard to filter through tasks to debug.
Alternative
If not possible we could use a cron that runs kubectl delete pod --field-selector=status.phase==Succeeded -n waypoint.
Additional context
After a deployment using an ODR Task the container’s last state is “Succeeded”, and there ends up being hundreds of these lingering around. Each deployment task spins up a new container called waypoint-task-<ID>.
Issue On demand runner task containers seem to stay in "Succeed" status and do not auto clean. There ends up being 100's of containers in the Waypoint namespace which makes it hard to filter through tasks to debug.
Solution Can there be a TTL on these containers? As mentioned in: https://kubernetes.io/docs/concepts/workloads/controllers/job/#clean-up-finished-jobs-automatically
Alternative If not possible we could use a cron that runs
kubectl delete pod --field-selector=status.phase==Succeeded -n waypoint
.Additional context After a deployment using an ODR Task the container’s last state is “Succeeded”, and there ends up being hundreds of these lingering around. Each deployment task spins up a new container called
waypoint-task-<ID>
.