Skip to content
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

Grim reaper #120

Open
wneirynck opened this issue Mar 26, 2024 · 0 comments
Open

Grim reaper #120

wneirynck opened this issue Mar 26, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@wneirynck
Copy link
Contributor

Even though there are plenty of checks, it may occur that a container instance keeps on running forever. This may happen for example when the process that is checking the termination (script or api) is killed or restarted. For this, we should have a "grim reaper" that checks if there are any dangling containers that need to be killed off. This could for example be run as a kubernetes cronjob. It should check all container instances that have been running longer than the configured timeout. It could possible mark the related builds as ended.

@wneirynck wneirynck added the enhancement New feature or request label Mar 26, 2024
This was referenced Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant