Skip to content
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

Set pod affinity for host assisted clone source pods #2576

Closed
akalenyu opened this issue Feb 7, 2023 · 2 comments · Fixed by #2647
Closed

Set pod affinity for host assisted clone source pods #2576

akalenyu opened this issue Feb 7, 2023 · 2 comments · Fixed by #2647
Assignees

Comments

@akalenyu
Copy link
Collaborator

akalenyu commented Feb 7, 2023

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 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)

@akalenyu
Copy link
Collaborator Author

akalenyu commented Feb 7, 2023

/good-first-issue

@ido106
Copy link
Contributor

ido106 commented Mar 5, 2023

/assign ido106

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants