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

update environment-idling.md #3730

Merged
merged 2 commits into from
Jun 7, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions docs/concepts-advanced/environment-idling.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,6 @@ The un-idling will take a couple of seconds, as the Kubernetes cluster needs to

### Can I disable / prevent the Idler from idling my environment?

Yes, there is a field `autoIdle` on the project \(impacts all environments\) and environment \(if you need to target just one 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 `0`
The default is always `1`\(idling is enabled\).
The field `autoIdle` can be set at the project level \(impacts all environments\) or for a single environment \(target just one 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`, then all environments will never be idled. The default value is `1` \(idling is enabled\).

Talk to your Lagoon administrator if you are unsure how to set these project/environment fields.