You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we idle projects pretty fast after not receiving traffic.
We discussed that we should not idle the mysql pods as they take the most time to start back up again.
Also the idling might be happening to fast so we can idle projects after 4 hours after the last traffic occured.
To control the idling further (i.e. not just running it with --all) we could put a label in place on the services allow-idler which would be overrideable via a label.
This way we could use allow-idler: yes for service that may be idled and allow-idler:no for services that should not be idled automatically.
The text was updated successfully, but these errors were encountered:
what is the use case for allowing the client to enable or disable auto idling specifically for single services? we will have global disabled services (like mysql) and project wide idling disabled, not sure if a specific service based one is really needed. Let's implement the MVP and implement in here:
Currently we idle projects pretty fast after not receiving traffic.
We discussed that we should not idle the mysql pods as they take the most time to start back up again.
Also the idling might be happening to fast so we can idle projects after 4 hours after the last traffic occured.
To control the idling further (i.e. not just running it with --all) we could put a label in place on the services
allow-idler
which would be overrideable via a label.This way we could use
allow-idler: yes
for service that may be idled andallow-idler:no
for services that should not be idled automatically.The text was updated successfully, but these errors were encountered: