-
Notifications
You must be signed in to change notification settings - Fork 288
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 docs for pod integration #1103
Conversation
✅ Deploy Preview for kubernetes-sigs-kueue ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Hi @achernevskii. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
Please change the target of the PR to the |
We changed the process here. Please rebase and target the |
/release-note-none |
27932b7
to
206a407
Compare
206a407
to
e11c93e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@achernevskii Is this still WIP?
Nope. Removed the WIP prefix |
- key: kueue-job | ||
operator: In | ||
values: [ "true", "True", "yes" ] | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mention that Pods that belong to some CRDs that we manage are excluded from being queued.
And that kueue adds a label to indicate which nodes are managed.
and enable the `pod` integration. | ||
|
||
Example `integrations` section of manager configuration with enabled pod integration: | ||
```yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add the top level fields, like kind
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should I create a minimal working configuration, or just add some of the top level fields?
Should we do the same thing for the following pages?
run_mpijobs.md
run_jobsets.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just the top level fields, to have a good context of where in the configuration integrations
fit.
Yes, we should probably do the same for others. You can do that in a follow up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated example configuration in adfe10d
|
||
### c. Limitations | ||
|
||
- A Kueue managed Pod cannot be created in `kube-system` or `kueue-system` namespaces. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mention that preemption actually terminates and deletes the pod.
When mentioning preemption, link to the documentation related to it.
12e9a29
to
adfe10d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: achernevskii, alculquicondor The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
LGTM label has been added. Git tree hash: 686746bba80c6e095c95eb347ba271a5cc240ff2
|
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Added documentation for pod integration.
Which issue(s) this PR fixes:
Related issue: #976
Special notes for your reviewer:
Does this PR introduce a user-facing change?