* Update Job docs to include info about using a headless service to enable pod communication via pod hostnames
* Change section title
* fix phrasing
* update yaml example
* update label selector
* more specific phrasing
* address comments and add new example
* add note about pod dns policies
* minor fixes
* add link to job patterns
* Update content/en/docs/tasks/job/intra-job-pod-networking-using-pod-hostnames.md
Co-authored-by: Aldo Culquicondor <1299064+alculquicondor@users.noreply.github.com>
* Update content/en/docs/tasks/job/intra-job-pod-networking-using-pod-hostnames.md
Co-authored-by: Aldo Culquicondor <1299064+alculquicondor@users.noreply.github.com>
* Update content/en/docs/tasks/job/intra-job-pod-networking-using-pod-hostnames.md
Co-authored-by: Aldo Culquicondor <1299064+alculquicondor@users.noreply.github.com>
* Update content/en/docs/tasks/job/intra-job-pod-networking-using-pod-hostnames.md
Co-authored-by: Aldo Culquicondor <1299064+alculquicondor@users.noreply.github.com>
* Update content/en/docs/concepts/workloads/controllers/job.md
Co-authored-by: Aldo Culquicondor <1299064+alculquicondor@users.noreply.github.com>
* address comments
* clarify sentence
* move minikube note to prereqs
* address comments
* captitalize all instances of Job
* move minikube notes to bottom of prereqs
* address comments
* update example
* fix typo
* update phrasing
* link to this from the completion modes section of the job docs
* address phrasing comments
* add newlines to break up block of text
* update phrasing
* update phrasing
* Update content/en/docs/concepts/workloads/controllers/job.md
Co-authored-by: Qiming Teng <tengqm@outlook.com>
* Update content/en/docs/tasks/job/job-with-pod-to-pod-communication.md
Co-authored-by: Qiming Teng <tengqm@outlook.com>
* Update content/en/docs/tasks/job/job-with-pod-to-pod-communication.md
Co-authored-by: Qiming Teng <tengqm@outlook.com>
* Update content/en/docs/tasks/job/job-with-pod-to-pod-communication.md
Co-authored-by: Qiming Teng <tengqm@outlook.com>
* Update content/en/docs/tasks/job/job-with-pod-to-pod-communication.md
Co-authored-by: Qiming Teng <tengqm@outlook.com>
* Update content/en/docs/tasks/job/job-with-pod-to-pod-communication.md
Co-authored-by: Qiming Teng <tengqm@outlook.com>
* Update content/en/docs/tasks/job/job-with-pod-to-pod-communication.md
Co-authored-by: Qiming Teng <tengqm@outlook.com>
* Update content/en/docs/tasks/job/job-with-pod-to-pod-communication.md
Co-authored-by: Qiming Teng <tengqm@outlook.com>
* Update content/en/docs/tasks/job/job-with-pod-to-pod-communication.md
Co-authored-by: Qiming Teng <tengqm@outlook.com>
Co-authored-by: Aldo Culquicondor <1299064+alculquicondor@users.noreply.github.com>
Co-authored-by: Qiming Teng <tengqm@outlook.com>
Be more explicit on the "duplicate endpoints" sections about what are the consumers expectations and the need to parse all the list of slices and remove only the duplicates
Migrate away:
- details of virtual IP mechanism for Services
- detailed information about protocols for Services (UDP, TCP, SCTP)
Co-authored-by: Antonio Ojea <aojea@redhat.com>
Co-authored-by: Qiming Teng <tengqm@outlook.com>
A debugging rabbit hole lead me to digging around kublet's behavior
regarding certain DNS Policies.
This commit updates some potentially misleading wordings to more
correctly convey kubelet's behavior which was discovered after some
rabbit hole debugging of DNS Policies.
The ClusterFirst policy documentation would imply that the resolve.conf
of a Pod would contain a fallback to the Node's nameserver. This is not
the cause, [kubelet explicitly
mentions](4276ed3628/pkg/kubelet/network/dns/dns.go (L403-L407))
that the fallback is handled by whatever system is running kube-dns or
coredns which dramatically changes the behavior of the system when the
cluster's DNS is unavailable.
The ClusterFirstWithHostNet policy is lacking any amount of detail as to
why one would desire to use it. This commit doesn't go into complete
detail but adds an important note about the behavior of `hostNetwork`
when not using the `ClusterFirstWIthHostNet` Policy.