Introducing a ReclaimPolicy
for ephemerally created Volume
resource
#1153
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.
Proposed Changes
ReclaimPolicy
for ephemerally createdVolume
resource with 2 supported modes:Retain
: the resource is not deleted after the managing resource has been deletedDelete
: the current behavior, the resource is garbage-collected when the managing resource has been deletedReclaimPolicy
would be assumed to beDelete
to not to not break current behavior.OwnerReference
is added to ephemerally created volume only in case ofReclaimPolicy
is set toDelete
VolumeTemplateSpec
to supportReclaimPolicy
type along with existing VolumeSpec[Note: volume_release_controller is already taking care of releasing volumes whose claimer doesn't existing, by setting .spec.claimRef to nil when claimer
Machine
object is deleted. So not adding any extra logic for this]Fixes #1114