feat: Add new cacheTtlMinutes and cacheJitterMaxMinutes configuration options #847
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.
Add configurable cache TTL and jitter settings.
Problem
Currently, the image existence cache has a hardcoded TTL of 24 hours with a 3-hour jitter. This can be problematic for users who:
Solution
Added two new configuration options:
cacheTtlMinutes
(default: 1440 - 24 hours): Controls how long image existence information is cachedcacheJitterMaxMinutes
(default: 180 - 3 hours): Controls the maximum random time added to prevent cache stampedeBoth settings are configurable via the
.k8s-image-swapper.yaml
config file. Once this gets reviewed I'll make some updates to the helm-chart to support these new configuration values.Fixes #843