Is your feature request related to a problem? Please describe.
As a CSI consumer, I hope it can provide a method to taint a disk drive and mark it unschedulable, possibly by using a label. With the disk marked, no new PV will be allocated from the drive, but it won't affect existing PVs.
This may provide a choice for applications when they encounter disk read/write errors. There might be a time gap between application hitting a disk error and CSI disk replacement workflow taking place. If an application can only wait for CSI disk replacement, it may need to panic on disk error situation repeatedly for a while, or use fake-attach method but with the risk of losing data. The application may want to proactively restart with new PVs scheduled on other healthy drives. So it needs to avoid being scheduled to the same drive.
Acceptance Criteria:
feature usage is documented.
implementation is done in which a disk can be marked as unschedulable, no new PVs will be allocated from this disk, but existing PVs won't be affected.
the implementation conforms to CSI spec
Describe the solution you'd like
I hope it can provide a method to taint a disk drive and mark it unschedulable, possibly by using a label. With the disk marked, no new PV will be allocated from the drive, but it won't affect existing PVs.
Is your feature request related to a problem? Please describe.
As a CSI consumer, I hope it can provide a method to taint a disk drive and mark it unschedulable, possibly by using a label. With the disk marked, no new PV will be allocated from the drive, but it won't affect existing PVs.
This may provide a choice for applications when they encounter disk read/write errors. There might be a time gap between application hitting a disk error and CSI disk replacement workflow taking place. If an application can only wait for CSI disk replacement, it may need to panic on disk error situation repeatedly for a while, or use fake-attach method but with the risk of losing data. The application may want to proactively restart with new PVs scheduled on other healthy drives. So it needs to avoid being scheduled to the same drive.
Acceptance Criteria:
feature usage is documented. implementation is done in which a disk can be marked as unschedulable, no new PVs will be allocated from this disk, but existing PVs won't be affected. the implementation conforms to CSI spec
Describe the solution you'd like I hope it can provide a method to taint a disk drive and mark it unschedulable, possibly by using a label. With the disk marked, no new PV will be allocated from the drive, but it won't affect existing PVs.
Describe alternatives you've considered None.
Additional context None.