-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Update Job docs to include info about enabling pod-to-pod communication within a job using pod hostnames #37771
Conversation
…ble pod communication via pod hostnames
Welcome @danielvegamyhre! |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
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.
Please sign CLA
/check-cla |
Signed CLA |
/assign @sftim |
/assign @alculquicondor |
LGTM label has been added. Git tree hash: 1c607dc3aa8270b66d40d86873c12c0a3902b402
|
@alculquicondor I made one final small change to make and this accidentally removed your LGTM, sorry! |
That's ok, you still need editorial approval for sig-docs. They will add the LGTM back, once they review, based on my comment. |
@sftim this is ready for sig-docs to take a look, see LGTM from job-controller approver above |
|
||
[Queue with Pod Per Work Item]: /docs/tasks/job/coarse-parallel-processing-work-queue/ | ||
[Queue with Variable Pod Count]: /docs/tasks/job/fine-parallel-processing-work-queue/ | ||
[Indexed Job with Static Work Assignment]: /docs/tasks/job/indexed-parallel-processing-static/ | ||
[Job Template Expansion]: /docs/tasks/job/parallel-processing-expansion/ | ||
[Job with Pod-to-Pod Communication]: /docs/tasks/job/job-with-pod-to-pod-communication/ |
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.
Remove this line
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.
If I remove this line, the references to "Job with Pod-to-Pod Communication" will show up as string literals, rather than as links. Can you clarify why you want to remove it?
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.
Line 267 is already a complete link.
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.
I guess the solution is rather the opposite: remove the complete link from line 267
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.
Em... both are valid markdown syntax. The full link syntax is preferred over the out-of-band link syntax because we have scripts to scan bad links and that script is not good at handling the out-of-band syntax.
Co-authored-by: Qiming Teng <tengqm@outlook.com>
Co-authored-by: Qiming Teng <tengqm@outlook.com>
Co-authored-by: Qiming Teng <tengqm@outlook.com>
Co-authored-by: Qiming Teng <tengqm@outlook.com>
Co-authored-by: Qiming Teng <tengqm@outlook.com>
Co-authored-by: Qiming Teng <tengqm@outlook.com>
Co-authored-by: Qiming Teng <tengqm@outlook.com>
Co-authored-by: Qiming Teng <tengqm@outlook.com>
Co-authored-by: Qiming Teng <tengqm@outlook.com>
This one is ready to go, given tech/doc review history. |
LGTM label has been added. Git tree hash: 8a840338865c699b0b577ee5013ca8f580b11a65
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tengqm 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 |
There is a format error, PTAL at fix #38195 |
The purpose of these changes is to update the Job docs to include information about how to enable pod communication within a Job using pod hostnames. This requires setting up a headless service, and setting the Job template spec to specify the headless service name as a subdomain. Doing so will trigger kube-dns to cache the pod hostnames, and enable pod-to-pod communication via
<podHostname>.<headlessServiceName>
format.This is currently undocumented, so these changes outline the steps to set this up, as well as a working example.