We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
1、When there are multiple pods in the resource type deployment, the statistics cover them and an alarm will be triggered. This is not the actual number limit of k8s nodes. https://runbooks.prometheus-operator.dev/runbooks/kubernetes/kubelettoomanypods/
2、The current number of pods in my cluster is 73, which does not reach the pod number limit of the node node.
3、This is the threshold reached in the alarm. All alarms should be issued based on the total number of pods on the node and the actual number of pods.
4、kubelet_running_pods Reference change indicator
The text was updated successfully, but these errors were encountered:
Hi, that is being pulled in from mixin https://github.com/kubernetes-monitoring/kubernetes-mixin/blob/a3fbf21977deb89b7d843eb8371170c011ea6835/alerts/kubelet.libsonnet#L51 so might be worth reporting the issue there.
Sorry, something went wrong.
No branches or pull requests
1、When there are multiple pods in the resource type deployment, the statistics cover them and an alarm will be triggered. This is not the actual number limit of k8s nodes.
https://runbooks.prometheus-operator.dev/runbooks/kubernetes/kubelettoomanypods/
2、The current number of pods in my cluster is 73, which does not reach the pod number limit of the node node.
3、This is the threshold reached in the alarm. All alarms should be issued based on the total number of pods on the node and the actual number of pods.
4、kubelet_running_pods Reference change indicator
The text was updated successfully, but these errors were encountered: