One of the important metrics that may suggest overload of the control plane is the number of watches that are closed by kube-apiserver because they don't keep up (or watchcache itself is not keeping).
We want to add a check to our tests that will be validating if this metrics is not too high.
Metrics to exercise:
The easiest way to do it is probably add to prometheus-based measurement, but @marseel to confirm.
One of the important metrics that may suggest overload of the control plane is the number of watches that are closed by kube-apiserver because they don't keep up (or watchcache itself is not keeping).
We want to add a check to our tests that will be validating if this metrics is not too high.
Metrics to exercise:
The easiest way to do it is probably add to prometheus-based measurement, but @marseel to confirm.