Auto-disable maintenance after services are UP #2603

New issue

Open

opened 2026-02-28 03:00:30 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-28 03:00:30 -05:00

Owner

Originally created by @shalak on GitHub (Sep 19, 2023).

⚠️ Please verify that this feature request has NOT been suggested before.

I checked and didn't find similar feature request

🏷️ Feature Request Type

Other

🔖 Feature description

Usual update flow in my environment looks like this:

I go to Kuma's Maintenance section
I start manual Maintenance mode
I update my services
I forgot to stop the Maintenance mode even though the services are UP after a while

As a result my service is not monitored :)

✔️ Solution

The manual maintenance mode should have an option to auto-disable itself once the services-under-maintenance reply with OK statuses. Of course, there should be some kind of grace/warmup period, so it doesn't trigger immediately between steps 3 and 4 mentioned above (i.e. I've already started the manual maintenance mode, but didn't start updating my services yet).

❓ Alternatives

Unfortunately, I couldn't find any alternative solution to this problem

📝 Additional Context

No response

Originally created by @shalak on GitHub (Sep 19, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type Other ### 🔖 Feature description Usual update flow in my environment looks like this: 1. I go to Kuma's Maintenance section 2. I start manual Maintenance mode 3. I update my services 4. I forgot to stop the Maintenance mode even though the services are UP after a while As a result my service is not monitored :) ### ✔️ Solution The manual maintenance mode should have an option to auto-disable itself once the services-under-maintenance reply with OK statuses. Of course, there should be some kind of grace/warmup period, so it doesn't trigger immediately between steps 3 and 4 mentioned above (i.e. I've already started the manual maintenance mode, but didn't start updating my services yet). ### ❓ Alternatives Unfortunately, I couldn't find any alternative solution to this problem ### 📝 Additional Context _No response_