Assume detached state on 404 during ControllerUnpublishVolume #221
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously we would bubble up 404 HTTP response codes during controller unpublish (i.e., volume detachment) events as errors to the invoking external-provisioner, causing the sidecar to go into an infinite retry loop. This change short-circuits the behavior by returning a success message to the caller.
One case where we see the problematic behavior occurring is when users detach volumes directly (i.e., outside of Kubernetes).