-
Notifications
You must be signed in to change notification settings - Fork 17
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
remove VA deletion #158
remove VA deletion #158
Conversation
Signed-off-by: Michael Shitrit <[email protected]>
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mshitrit The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test 4.12-openshift-e2e |
Would it make more sense to move |
I have no strong opinion either way. |
Signed-off-by: Michael Shitrit <[email protected]>
/test 4.12-openshift-e2e |
Can you update commons and use |
/lgtm Just leaving the time to close the other threads |
/unhold |
/hold |
Signed-off-by: Michael Shitrit <[email protected]>
/lgtm |
/unhold |
ECOPROJECT-1748
VA should not be deleted by SNR. kube-control-manager (KCM) detects the pod deletion and automatically detaches the VAs which are not connected to any pod, forcefully deleting the VA has the risk of interfering with the process of detaching the VAs.