k8s-triage-robot
commented
8 months ago The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
AndrewSirenko
Is your feature request related to a problem? Please describe.
AWS exposes volume status via
describe-volume-status. AFAIK this (and the UI) is the only way to observe volume impaired status.The aws-ebs-csi-driver seems like a good place to collect and expose this information. @ConnorJC3 already made a PR to do this but it went stale and was closed. Would love to see that work revived and merged:
Describe the solution you'd like in detail
I think that https://github.com/kubernetes-sigs/aws-ebs-csi-driver/pull/1495 does everything I need. An additional nice feature would be the option to enable monitoring on a per-volume basis. This would potentially reduce the expense associated with the additional API calls, and allow the enable volume monitoring only where volume health is critical.