Jan Šafránek

Question is, do you expect the node to come back and optimize for this case? That's manageable.

> The original motivation for https://github.com/kubernetes-sigs/sig-storage-lib-external-provisioner/issues/121 was for the autoscaling case where the node never comes back That's the hard case. The provisioner lib then needs to store the whole...

Question is, if `selectedNode` annotation is valid when someone deletes a node and creates a new one with the same name. Assuming yes, the new node is still the right...

> And so the question is for the non-final case, should we retry the CreateVolume() call with the old node (Jan's proposal), or get a new node from the scheduler...

/lgtm /approve

Thanks a lot !

I am sorry, @rlia can you please rebase?

/sig storage

/label lead-opted-in /milestone v1.27 /stage alpha

> This enhancement is targeting for stage alpha for 1.27 (correct me, if otherwise) We're targeting Beta directly, we had alpha as part of https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1710-selinux-relabeling And the KEP is merged,...