github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-08-01 07:47:56 +00:00
Code Issues Projects Releases Wiki Activity

update service&endpoint describe

Browse Source
This commit is contained in:
jijun2 2015-09-28 23:55:08 -04:00
parent 095fec84e9
commit d624bee753
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/user-guide/services.md
View File

@ -208,11 +208,11 @@ this example).
Every node in a Kubernetes cluster runs a `kube-proxy`. This application Every node in a Kubernetes cluster runs a `kube-proxy`. This application
watches the Kubernetes master for the addition and removal of `Service` watches the Kubernetes master for the addition and removal of `Service`
and `Endpoints` objects. For each `Service` it opens a port (randomly chosen) and `Endpoints` objects. For each `Service` it opens a port (randomly chosen)
on the local node. Any connections made to that port will be proxied to one of on the local node. Any connections to `service` port will be proxied to one of
the corresponding backend `Pods`. Which backend to use is decided based on the the corresponding backend `Pods`. Which backend `Pod` to use is decided based on the
`SessionAffinity` of the `Service`. Lastly, it installs iptables rules which `SessionAffinity` of the `Service`. Lastly, it installs iptables rules which
capture traffic to the `Service`'s cluster IP (which is virtual) and `Port` and capture traffic to the `Service`'s cluster IP (which is virtual) and `Port` then
redirects that traffic to the previously described port. redirects that traffic to the backend `Pod` (`Endpoints`).
The net result is that any traffic bound for the `Service` is proxied to an The net result is that any traffic bound for the `Service` is proxied to an
appropriate backend without the clients knowing anything about Kubernetes or appropriate backend without the clients knowing anything about Kubernetes or