Skip to content
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

RFE: Implementation of Volume Health Monitoring #874

Open
jakobmoellerdev opened this issue Apr 4, 2024 · 2 comments · May be fixed by #916
Open

RFE: Implementation of Volume Health Monitoring #874

jakobmoellerdev opened this issue Apr 4, 2024 · 2 comments · May be fixed by #916

Comments

@jakobmoellerdev
Copy link
Contributor

What should the feature do:

The CSI Specification has added an alpha feature for VolumeCondition monitoring. This has been adopted in kubernetes into alpha grade as of 1.21 https://kubernetes.io/docs/concepts/storage/volume-health-monitoring/

I would like to propose implementation of the VOLUME_CONDITION capability in the node server of TopoLVM in order to leverage this feature, but propose it as alpha grade.

What is use case behind this feature:

I think we could add VolumeCondition monitoring into TopoLVM in order to allow reporting abnormal volume statuses of the underlying logical volumes and volume groups via Events. to make transparent to the user whats wrong.

E.g. after a node reboot, if the LV activation fails, the volume event for an inactive logical volume could indicate to the user that remediation is necessary.

@jakobmoellerdev jakobmoellerdev changed the title Implementation of Volume Health Monitoring RFE: Implementation of Volume Health Monitoring Apr 5, 2024
@llamerada-jp
Copy link
Contributor

It looks good to output the activation state of the volume corresponding to the PV as shown in your example. As discussed in the related issue, I guess it is difficult to use SMART.

related issue
#316
#390

related KEP
https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1432-volume-health-monitor

Copy link
Contributor

github-actions bot commented May 9, 2024

This issue has been automatically marked as stale because it has not had any activity for 30 days. It will be closed in a week if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label May 9, 2024
@peng225 peng225 added keepalive and removed stale labels May 13, 2024
@jakobmoellerdev jakobmoellerdev linked a pull request May 15, 2024 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Waiting
Development

Successfully merging a pull request may close this issue.

3 participants