Lagoon automatically idles environments if they have been unused for a couple of hours. This is done in order to reduce the load on the Kubernetes clusters and improve the overall performance of production environments and development environments that are actually in use.
The Environment Idler has many different configuration capabilities. Here are the defaults of a standard Lagoon installation (these could be quite different in your Lagoon, check with your Lagoon administrator!)
Idling is tried every 4 hours.
Production environments are never idled.
CLI pods are idled if they don't include a cronjob and if there is no remote shell connection active.
All other services and pods are idled if there was no traffic on the environment in the last 4 hours.
If there is an active build happening, there will be no idling.
The Lagoon Idler will automatically un-idle an environment as soon as it is visited, therefore just visiting any URL of the environment will start the environment.
The un-idling will take a couple of seconds, as the Kubernetes cluster needs to start all containers again. During this time there will be waiting screen shown to the visitor that their environment is currently started.
Yes, there is a field
autoIdle on the project (impacts all environments) and environment (if you need to target just 1 environment), as to whether idling is allowed to take place. A value of
1 indicates the project/environment is eligible for idling. If the project is set to
0 the environments will never be idled, even if the environment is set to
The default is always
1(idling is enabled).
Talk to your Lagoon administrator if you are unsure how to set these project/environment fields.