backport [release-v1.11.x]: feat: expose subnet refresh interval as configurable setting (#9150) - #9521
Open
DerekFrank wants to merge 2 commits into
Open
Conversation
Adds SUBNET_REFRESH_INTERVAL (--subnet-refresh-interval, default 1m) to control how often Karpenter refreshes subnet data from EC2. This allows operators running large fleets in shared accounts to reduce DescribeSubnets API call volume by accepting longer subnet staleness. All three subnet provider caches (subnet list, available IP counts, and public IP association) use the same interval since they are all populated from a single DescribeSubnets response. (cherry picked from commit 01c0508) Backport of aws#9150 onto release-v1.11.x (subnetRefreshInterval only; amiRefreshInterval/enableZonalShift not present in 1.11).
DerekFrank
commented
Aug 19, 2026
DerekFrank
left a comment
DerekFrank
left a comment
Member
Author
There was a problem hiding this comment.
/karpenter snapshot
Contributor
|
Snapshot successfully published to |
Adds SECURITY_GROUP_REFRESH_INTERVAL (--security-group-refresh-interval, default 1m) to control how often Karpenter refreshes security group data from EC2, mirroring the subnet-refresh-interval knob. Operators running large fleets in shared accounts can raise this to reduce DescribeSecurityGroups API call volume by accepting longer staleness. The security group provider uses a single cache; its TTL is now driven by the configured interval instead of the fixed DefaultTTL. Validated >= 1m. Companion to the subnet-refresh-interval backport (aws#9150) on release-v1.11.x.
DerekFrank
commented
Aug 20, 2026
DerekFrank
left a comment
DerekFrank
left a comment
Member
Author
There was a problem hiding this comment.
/karpenter snapshot
Contributor
|
Snapshot successfully published to |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Backport of #9150 onto `release-v1.11.x`.
Adds `SUBNET_REFRESH_INTERVAL` (`--subnet-refresh-interval`, default `1m`) to control how often Karpenter refreshes subnet data from EC2, letting operators running large fleets in shared accounts reduce DescribeSubnets API call volume by accepting longer subnet staleness. All three subnet provider caches (subnet list, available IP counts, public IP association) are populated from a single DescribeSubnets response — the list cache uses the interval directly; the IP / public-IP caches use `max(interval, original TTL)`.
Backport notes
Cherry-picked from commit `01c0508c8d2c91f744a115fa69c8ecc03d3a37d2`. Conflicts resolved against 1.11:
Testing