From 3dea3dbf9402cc5be06171859c49a635a6f8bff6 Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Thu, 1 Aug 2019 22:39:18 +0100 Subject: [PATCH] Tidy headless Service example (#15082) --- content/en/docs/concepts/services-networking/service.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md index a0474ec11a..4800af5628 100644 --- a/content/en/docs/concepts/services-networking/service.md +++ b/content/en/docs/concepts/services-networking/service.md @@ -431,14 +431,12 @@ this case, you can create what are termed “headless” Services, by explicitly specifying `"None"` for the cluster IP (`.spec.clusterIP`). You can use a headless Service to interface with other service discovery mechanisms, -without being tied to Kubernetes' implementation. For example, you could implement -a custom {{< glossary_tooltip term_id="operator-pattern" text="Operator" >}} upon -this API. +without being tied to Kubernetes' implementation. -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 for them. How DNS is automatically configured depends on whether the Service has -selectors defined. +selectors defined: ### With selectors