Geoff Webster

This would be useful, we have a lot of DaemonSets with services that are causing constant reconciliations due to constant cluster scaling.

Could this also happen if you: 1. Run aws sso login 2. Close the auto-opened Device Auth page 3. Open the URL manually 4. Copy Code I just tried that...

This also has a massive hit on the Metrics Envoy ends up emitting, mostly worthless. Is there anyway that can be stemmed separate from Envoy's config?

Not stale

Let me see, I have to go through my legal team first before we can submit PRs upstream.

Looks like this just needs to be documented that they are published to GCS: https://github.com/kubernetes/cloud-provider-aws/pull/568#issuecomment-1510407037

Might be good to add that to the readme description, a lot of tooling in this space folks might assume its talking about actual utilization vs allocations.

Looks like it just needs to call out that it needs to use the Kubernetes label format, not the exported label format as ingested by Prometheus/exposed by KSM.

With server side apply becoming more common, wouldn't those resources be missed by kubent since it does not rely on this annotation?

/remove-lifecycle rotten Pending confirmation this is fixed in 1.30+