Feature Overview (aka. Goal Summary)  

Allow disabling force detach of volumes in Openshift clusters.

when a node is non-responsive (or more precisely when kubelet is non-responsive or not running), after a pod is deleted the volume can be force detached from the node even though it may be mounted on the node.

Goals (aka. expected user outcomes)

Expose an option to disable force detach to OCP admins

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

OCP admins can easy disable force detach cluster wide

Out of Scope

limited to the KCM disable-force-detach-on-timeout option

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

We've seen issues with certain drivers where the volume is force detached while the volume is still mounted leading to data corruption

https://issues.redhat.com/browse/OCPBUGS-61077

RFE: https://issues.redhat.com/browse/RFE-8138

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

We shouldn't change the option

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

Explain how to disable force detach, when is it relevant and what are the impacts. Also link to node graceful shutdown doc?

Interoperability Considerations

N/A