Skip to content

Support health monitoring with external-health-monitor-controller #1712

@maxenglander

Description

@maxenglander

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 #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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions