whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Tidy headless Service example (#15082)

Browse Source
This commit is contained in:
Tim Bannister
2019-08-01 22:39:18 +01:00
committed by Kubernetes Prow Robot
parent 8670391e2a
commit 3dea3dbf94
1 changed files with 3 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/services-networking/service.md
+3 -5
View File
@@ -431,14 +431,12 @@ this case, you can create what are termed “headless” Services, by explicitly
specifying `"None"` for the cluster IP (`.spec.clusterIP`). specifying `"None"` for the cluster IP (`.spec.clusterIP`).
You can use a headless Service to interface with other service discovery mechanisms, You can use a headless Service to interface with other service discovery mechanisms,
without being tied to Kubernetes' implementation. For example, you could implement without being tied to Kubernetes' implementation.
a custom {{< glossary_tooltip term_id="operator-pattern" text="Operator" >}} upon
this API.
For such `Services`, a cluster IP is not allocated, kube-proxy does not handle For headless `Services`, a cluster IP is not allocated, kube-proxy does not handle
these Services, and there is no load balancing or proxying done by the platform these Services, and there is no load balancing or proxying done by the platform
for them. How DNS is automatically configured depends on whether the Service has for them. How DNS is automatically configured depends on whether the Service has
selectors defined. selectors defined:
### With selectors ### With selectors