From 191eca8322a2e1c109aedfc7541a0ae3590db99d Mon Sep 17 00:00:00 2001 From: Qiming Date: Tue, 10 Apr 2018 04:10:11 +0800 Subject: [PATCH] Document limitations of services without selectors (#8028) Based on the discussion on kubernetes/kubernetes#40870, we'd better clearly document that the endpoint IPs used by a service without selectors cannot be virtual ones. --- docs/concepts/services-networking/service.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/concepts/services-networking/service.md b/docs/concepts/services-networking/service.md index 555c485ec9..4aab078f12 100644 --- a/docs/concepts/services-networking/service.md +++ b/docs/concepts/services-networking/service.md @@ -117,8 +117,11 @@ subsets: - port: 9376 ``` -**NOTE:** Endpoint IPs may not be loopback (127.0.0.0/8), link-local -(169.254.0.0/16), or link-local multicast (224.0.0.0/24). +**NOTE** The endpoint IPs may not be loopback (127.0.0.0/8), link-local +(169.254.0.0/16), or link-local multicast (224.0.0.0/24). They cannot be the +cluster IPs of other Kubernetes services either because the `kube-proxy` +component doesn't support virtual IPs as destination yet. +{: .note} Accessing a `Service` without a selector works the same as if it had a selector. The traffic will be routed to endpoints defined by the user (`1.2.3.4:9376` in