Update service.md (#15267)
parent
e50dba3ac4
commit
24d32ebd83
|
@ -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
|
||||
|
|
Loading…
Reference in New Issue