Provide metrics for the network bandwidth usage between the api server and etcd #15
Labels
kind/enhancement
Enhancement, improvement, extension
lifecycle/rotten
Nobody worked on this for 12 months (final aging stage)
What would you like to be added
Provide metrics for end users so that they can check which api server requests contribute to the network bandwidth usage between the api server and etcd.
Why is this needed
The api server uses in-memory filtering for list requests with label selectors, so that client requests that seem to be reasonable and have a small response size can still incur a high bandwidth usage in the "backend": between the api server and etcd. (See gardener/gardener#5374)
We have seen that when the network link between the api server and etcd is saturated, multiple components start to fail.
The goal of this issue is to provide metrics for shoot owners so that they can identify the clients that contribute to the excessive network usage and can optimize their requests accordingly.
The text was updated successfully, but these errors were encountered: