AggregatedAPIDown rule constantly fire on kubernetes < 1.18 due to k8s bug fixed in 1.18. See https://github.com/kubernetes/kubernetes/pull/87778 and https://github.com/kubernetes/kube-aggregator/issues/23.
Helm chart should enable the rule only for kubernetes >= 1.18
initial it was addressed here:
https://github.com/kubernetes-monitoring/kubernetes-mixin/issues/397
so please make noise there too
also, there is slightly related issues https://github.com/helm/charts/issues/22081
they are not super active on fixing and syncing https://github.com/kubernetes-monitoring/kubernetes-mixin
into
https://github.com/coreos/kube-prometheus/blob/master/manifests/prometheus-rules.yaml
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.
bump
I'm still seeing it as well. We updated our k8s version to 1.15 and now this is always firing.
Experiencing this as well, Kubernetes 1.16. Can this be prioritized somehow, or is this not the right place to ask for it?
馃毀 This chart is now deprecated.
Further development has moved to prometheus-community/helm-charts. The chart has been renamed kube-prometheus-stack to more clearly reflect that it installs the kube-prometheus project stack, within which Prometheus Operator is only one component.
If applicable, please re-open this issue there. Thanks!
Most helpful comment
bump