-
Notifications
You must be signed in to change notification settings - Fork 47
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
Add concept doc on how exclusive placement works #458
Comments
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle stale |
/remove-lifecycle rotten |
/assign |
Is this issue meant to demonstrate how to use and operate, or is it to be explained through code? |
__
It's meant to explain how exclusive placement is implemented. I.e., a leader pod (index 0) from each Job is created, with pod affinity/anti-affinity rules ensuring only 1 leader pod lands in each topology domain (e.g., rack, node pool, etc). All follower pods (non-0 indexes) are blocked from creation until their corresponding leader pod has been scheduled. Once a leader pod from a job is scheduled, the follower pods in that Job will be created and have nodeSelectors injected which ensure they land in the same topology domain as the leader. |
OK, I understand, I will also demonstrate with examples |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
What would you like to be added:
Add concept doc on how exclusive placement works
Why is this needed:
Users often have questions about how it works and it is helpful info for them to be able to debug issues on their own
The text was updated successfully, but these errors were encountered: