New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[kube-prometheus-stack] kube-apiserver.rules is duplicate #1799
Comments
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. |
Issue is still there and relevant. |
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. |
This issue is being automatically closed due to inactivity. |
Describe the bug a clear and concise description of what the bug is.
The
kube-apiserver.rules
rule group is duplicated by thekube-apiserver-burnrate.rules
andkube-apiserver-histogram.rules
rule groups.In the upstream kubernetes-mixin, the
kube-apiserver.rules
were split into the other two in this commit: kubernetes-monitoring/kubernetes-mixin@2986c52It looks like the two new files were added, but the old/deprecated file was not removed in #1165
This causes unnecessary CPU load in our kube-prometheus-stack installation. In total the
rule evaluations
take ~40seconds for each interval, of thatkube-apiserver.rules
takes 20seconds and-burnrate.rules
+histogram.rules
together take another 20seconds. By removing the oldkube-apiserver.rules
file, we could reduce or rule evalutions time by 50%.What's your helm version?
v3.8.0
What's your kubectl version?
Which chart?
kube-prometheus-stack
What's the chart version?
32.2.0
What happened?
Duplicate rules for
apiserver_request:burnrateXX
andcluster_quantile:apiserver_request_duration_seconds:histogram_quantile
are deployed in the default configuration.What you expected to happen?
I expected no duplicate rules to be deployed.
How to reproduce it?
Deploy the default chart and observe the duplicated rules in prometheus.
Enter the changed values of values.yaml?
NONE
Enter the command that you execute and failing/misfunctioning.
Command executes successfully, issue is with the deployed AlertRules.
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: