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

Add concept doc on how exclusive placement works #458

Open
Tracked by #683
danielvegamyhre opened this issue Mar 15, 2024 · 10 comments
Open
Tracked by #683

Add concept doc on how exclusive placement works #458

danielvegamyhre opened this issue Mar 15, 2024 · 10 comments
Assignees

Comments

@danielvegamyhre
Copy link
Contributor

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

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 13, 2024
@k8s-triage-robot
Copy link

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:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 13, 2024
@danielvegamyhre
Copy link
Contributor Author

/remove-lifecycle stale

@danielvegamyhre
Copy link
Contributor Author

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jul 14, 2024
@googs1025
Copy link
Member

/assign
I will try this!

@googs1025
Copy link
Member

Is this issue meant to demonstrate how to use and operate, or is it to be explained through code?

@danielvegamyhre
Copy link
Contributor Author

__

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.

@googs1025
Copy link
Member

__

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

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 4, 2024
@danielvegamyhre
Copy link
Contributor Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants