-
Notifications
You must be signed in to change notification settings - Fork 111
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
*: Add runbook for KubePersistentVolumeInodesFillingUp #48
*: Add runbook for KubePersistentVolumeInodesFillingUp #48
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/retest-required Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
} | ||
``` | ||
|
||
You can inspect the status of the volume manually to determine which directory consumes large number of the inode: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
alerts/cluster-monitoring-operator/KubePersistentVolumeInodesFillingUp.md:31:81 MD013/line-length Line length [Expected: 80; Actual: 114]
alerts/cluster-monitoring-operator/KubePersistentVolumeInodesFillingUp.md:48:81 MD013/line-length Line length [Expected: 80; Actual: 196]
alerts/cluster-monitoring-operator/KubePersistentVolumeInodesFillingUp.md:49:81 MD013/line-length Line length [Expected: 80; Actual: 89]
/retest-required Please review the full test history for this PR and help us cut down flakes. |
5 similar comments
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
This is a newly added alert[1] and very similar to existing KubePersistentVolumeFillingUp but for inodes. [1] kubernetes-monitoring/kubernetes-mixin#761 Signed-off-by: Arunprasad Rajkumar <arajkuma@redhat.com>
db729f1
to
065ecd6
Compare
@arajkumar: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: arajkumar, simonpasquier The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hello, I just wanted to notify you that this alert will fire up needlessly in the event where the backing PVC can provide inodes dynamicaly and its metrics show I don't know if that's possible to ignore some types of volumes based on capabilities but you're the experts :) |
This is a newly added alert[1] and very similar to
existing KubePersistentVolumeFillingUp but for inodes.
[1] kubernetes-monitoring/kubernetes-mixin#761
Signed-off-by: Arunprasad Rajkumar arajkuma@redhat.com