[IMPROVEMENT] The auto-delete-pod-when-volume-detached-unexpectedly should only focus on the Kubernetes builtin workload. #12120
Metadata
Metadata
Assignees
Labels
System or volume resilienceVolume attach & detach relatedRequire to backport to 1.10.1 release branchRequest for improvement of existing functionMust be implement or fixed in this release (managed by PO)Require adding/updating auto e2e test cases if they can be automatedRequire backport. Only used when the specific versions to backport have not been definied.
Type
Fields
Give feedbackNo fields configured for Improvement.
Projects
Status
Is your improvement request related to a feature? Please describe (👍 if you like this request)
We noticed that the settings
auto-delete-pod-when-volume-detached-unexpectedlywill try to respawn some workload did not belong on kuberentes builtin. Like virt-launcher/hp-volume pod.It might cause some side effect like the VM might looks like reboot unexpectly.
So, we should focus on the kuberentes builtin workload with this setting.
Describe the solution you'd like
Only focus on the kuberentes builtin workload with setting
auto-delete-pod-when-volume-detached-unexpectedlyDescribe alternatives you've considered
No response
Additional context
cc @innobead, @derekbit