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

Document limitations of services without selectors (#8028)

Browse Source 
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.
This commit is contained in:
Qiming
2018-04-10 04:10:11 +08:00
committed by zacharysarah
parent cbd4aa3231
commit 191eca8322
1 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/concepts/services-networking/service.md
+5 -2
View File
@@ -117,8 +117,11 @@ subsets:
- port: 9376 - port: 9376
``` ```
**NOTE:** Endpoint IPs may not be loopback (127.0.0.0/8), link-local **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). (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. 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 The traffic will be routed to endpoints defined by the user (`1.2.3.4:9376` in