-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Exclude the metrics APIs from resources discovery #2606
Conversation
Thanks @stefanprodan ! It looks good, however I am not sure whether the specific discovery functions you are calling are cached (I vaguely recall that the memory-cache implementation of the discovery interface only applied caching to certain functions, and that's partly why I chose |
It uses the same client as before https://github.com/kubernetes/client-go/blob/master/discovery/discovery_client.go When enabling the go client logging the caller is:
|
1f7340f
to
db7d04d
Compare
db7d04d
to
ecd12bf
Compare
@squaremo anything else blocking this? I've rebase with master. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
anything else blocking this?
Nope, nothing blocking, just a suggestion for a minor tidy. Thanks Stefan 🍍
ecd12bf
to
dc8c1b9
Compare
This PR refactors the Kubernetes resources discovery to exclude the
*.metrics.k8s.io
API groups and thus avoiding querying the cluster metrics and failing to sync when the metrics providers are unavailable.Tested on EKS with metrics server and by @texasbobs with Prometheus adapter.
Fix: #2605
Fix: #2120
Fix: #2192