The stack configuration would have a section to define the actions to be taken when a service goes unhealthy: like restart the unhealthy service, the whole stack or just alert (current behavior).
It could even let you define how many restart attempts.
Thanks for the great work!
Originally created by @datascientist83 on GitHub (Sep 21, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/864
The stack configuration would have a section to define the actions to be taken when a service goes unhealthy: like restart the unhealthy service, the whole stack or just alert (current behavior).
It could even let you define how many restart attempts.
Thanks for the great work!
Second this - flexibility would be great (some stacks need restarting, some need redeploying, also doing this on individual containers or whole stacks would be useful).
<!-- gh-comment-id:3334590627 -->
@declan-wade commented on GitHub (Sep 25, 2025):
Second this - flexibility would be great (some stacks need restarting, some need redeploying, also doing this on individual containers or whole stacks would be useful).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @datascientist83 on GitHub (Sep 21, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/864
The stack configuration would have a section to define the actions to be taken when a service goes unhealthy: like restart the unhealthy service, the whole stack or just alert (current behavior).
It could even let you define how many restart attempts.
Thanks for the great work!
@declan-wade commented on GitHub (Sep 25, 2025):
Second this - flexibility would be great (some stacks need restarting, some need redeploying, also doing this on individual containers or whole stacks would be useful).
@GentleHoneyLover commented on GitHub (Oct 17, 2025):
This is something I am really missing in Komodo right now!