Disable capacity planning for kube_container_cpu
From the discussion in https://gitlab.com/gitlab-com/gl-infra/capacity-planning-trackers/gitlab-com/-/issues/1474#note_1720129998:
I think we need to tune this saturation point a bit more, a sidekiq pod using 100% of it's requested CPU isn't really a big problem, only if this happens to multiple pods over longer periods of time. I think we can lower the quantile for this.
@reprazent @hmerscher @rnaveiras
Are we doing the right thing in terms of saturation monitoring/capacity planning for kube_container_cpu
?
A few example warnings:
- https://gitlab.com/gitlab-com/gl-infra/capacity-planning-trackers/gitlab-com/-/issues/1474+
- https://gitlab.com/gitlab-com/gl-infra/capacity-planning-trackers/gitlab-com/-/issues/1582+
- https://gitlab.com/gitlab-com/gl-infra/capacity-planning-trackers/gitlab-com/-/issues/1651+
Are any of these actionable? If not, can we consider disabling capacity planning for these?