Keilan Jackson

Just experienced this on kube2iam 0.10.6, NOT running in EKS but with a kops cluster using weave. Most of our deployments were okay, but two of them were getting 500's...

I am very interested in a variable refresh feature - The solution proposed here would work for us: https://github.com/ben-manes/caffeine/issues/504#issuecomment-1086922055 Our use case is that we want to enable preloading about...

> The simplest way to do this is to delay the future by a random amount. A refresh is triggered as a reaction to a lookup which happens at an...

> If the data does not expire and you preload content, then you might simply have a scheduled task that reloads all contents (e.g. by inspecting the `cache.asMap()` view). Otherwise...

So I went and did a smoke test of this and it does speed up s3 quite a bit. It also makes us hit our rate limit on elb and...

The problem I'm seeing with the retries still is that we are still hitting the throttling limit, but just trying more times. Not sure that solution will work for something...

Any chance of this PR being considered? Would love to have this feature in our couchdb setups.

I ran into this same issue, is this fix still being considered?