kubernetes / kubernetes/perf-tests
Check watch terminations from clusters loader tests
Open
good first issue
help wanted
kind/feature
- Dominant language
- Go
- Stars
- 989
- Forks
- 654
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 56
Description
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:
- https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/storage/cacher/metrics.go#L58
- https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/storage/cacher/metrics.go#L94
The easiest way to do it is probably add to prometheus-based measurement, but @marseel to confirm.
Contributor guide
Assessment
This issue has not been assessed yet.