-
Feature
-
Resolution: Unresolved
-
Major
-
None
-
None
-
Product / Portfolio Work
-
None
-
0% To Do, 100% In Progress, 0% Done
-
False
-
-
False
-
S
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
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):
OCP admins can easy disable force detach cluster wide
| Deployment considerations | List applicable specific needs (N/A = not applicable) |
| Self-managed, managed, or both | both |
| Classic (standalone cluster) | yes |
| Hosted control planes | yes |
| Multi node, Compact (three node), or Single node (SNO), or all | all |
| Connected / Restricted Network | both |
| Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | all |
| Operator compatibility | not operator dependent |
| Backport needed (list applicable versions) | no |
| UI need (e.g. OpenShift Console, dynamic plugin, OCM) | no |
| Other (please specify) | n/a |
Out of Scope
limited to the KCM disable-force-detach-on-timeout option
Background
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
We shouldn't change the option
Documentation Considerations
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
- is depended on by
-
-
- Approved
-
- links to
