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

Update source-ip.md

Browse Source 
fix some typos
This commit is contained in:
linweibin
2017-08-14 17:32:56 +08:00
committed by Andrew Chen
parent 568d7d29ed
commit 56518164d3
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tutorials/services/source-ip.md
+3 -3
View File
@@ -121,7 +121,7 @@ $ NODEPORT=$(kubectl get -o jsonpath="{.spec.ports[0].nodePort}" services nodepo
$ NODES=$(kubectl get nodes -o jsonpath='{ $.items[*].status.addresses[?(@.type=="ExternalIP")].address }') $ NODES=$(kubectl get nodes -o jsonpath='{ $.items[*].status.addresses[?(@.type=="ExternalIP")].address }')
``` ```
if you're running on a cloudprovider, you may need to open up a firewall-rule If you're running on a cloudprovider, you may need to open up a firewall-rule
for the `nodes:nodeport` reported above. for the `nodes:nodeport` reported above.
Now you can try reaching the Service from outside the cluster through the node Now you can try reaching the Service from outside the cluster through the node
port allocated above. port allocated above.
@@ -181,7 +181,7 @@ client_address=104.132.1.79
``` ```
Note that you only got one reply, with the *right* client IP, from the one node on which the endpoint pod Note that you only got one reply, with the *right* client IP, from the one node on which the endpoint pod
is running on. is running.
This is what happens: This is what happens:
@@ -293,7 +293,7 @@ client_address=104.132.1.79
__Cross platform support__ __Cross platform support__
As of Kubernetes 1.5 support for source IP preservation through Services As of Kubernetes 1.5, support for source IP preservation through Services
with Type=LoadBalancer is only implemented in a subset of cloudproviders with Type=LoadBalancer is only implemented in a subset of cloudproviders
(GCP and Azure). The cloudprovider you're running on might fulfill the (GCP and Azure). The cloudprovider you're running on might fulfill the
request for a loadbalancer in a few different ways: request for a loadbalancer in a few different ways: