You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe:
Basically, the issue in kubernetes/kubernetes#103305 applies to CDI
in the concurrent host assisted clone use case, on storage that is not topology constrained (globally accessible from all nodes).
Consider the scenario:
Initiate 2 concurrent host assisted clone from source-pvc that was provisioned by rook-ceph-block with ReadWriteOnce
It is entirely possible that each of the pods lands on a different node, and thus one will remain pending
Describe alternatives you've considered:
A clear and concise description of any alternative solutions or features you've considered.
Additional context:
This is not a problem for topology constrained storage like HPP because scheduler will ensure
the pods land where the PV is (volume.kubernetes.io/selected-node ann)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe:
Basically, the issue in kubernetes/kubernetes#103305 applies to CDI
in the concurrent host assisted clone use case, on storage that is not topology constrained (globally accessible from all nodes).
Consider the scenario:
ReadWriteOnce
Describe the solution you'd like:
The suggested solution in hetznercloud/csi-driver#319 (comment)
Describe alternatives you've considered:
A clear and concise description of any alternative solutions or features you've considered.
Additional context:
This is not a problem for topology constrained storage like HPP because scheduler will ensure
the pods land where the PV is (
volume.kubernetes.io/selected-node
ann)The text was updated successfully, but these errors were encountered: