From 24d32ebd83d889975df588ecee53dc72ea9932a0 Mon Sep 17 00:00:00 2001 From: David Dieulivol Date: Sat, 6 Jul 2019 12:58:34 +0200 Subject: [PATCH] Update service.md (#15267) --- content/en/docs/concepts/services-networking/service.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md index befa87677b..b1a2cc0f90 100644 --- a/content/en/docs/concepts/services-networking/service.md +++ b/content/en/docs/concepts/services-networking/service.md @@ -432,8 +432,7 @@ 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 [Operator]( -to be built on the API). +a custom [Operator](https://coreos.com/operators/) to be built on the API. For such `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