Improvements to the service-idler #1139
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
This change allows the router-log query to logs-db to allow for an adjustable interval from 4h. In busy clusters it can be beneficial to idle environments sooner if they aren't being used as often.
It also adds 2 new checks
notin (mariadb,postgres)
have pods running greater than the default 4hr interval beforeThese 2 checks need to pass before it will continue to check
router-logs
and do the eventual idling.It adds the functionality to also force idling on services if required by using
./idle-services.sh force
Changelog Entry
Improvement - Allow adjustable interval in service idler (#1138)
Improvement - Check running builds and pods before idling (#1138)
Improvement - Allow services to be force idled manually
./idle-services.sh force
Closing issues
closes #1138