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

fix the command output (#9951)

Browse Source 
I have verified on version v1.11
This commit is contained in:
tanshanshan
2018-08-21 22:16:54 +08:00
committed by k8s-ci-robot
parent 1f56be2d06
commit a6411149a1
1 changed files with 13 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tutorials/services/source-ip.md
+13 -13
View File
@@ -35,7 +35,7 @@ IP of requests it receives through an HTTP header. You can create it as follows:
```console ```console
$ kubectl run source-ip-app --image=k8s.gcr.io/echoserver:1.4 $ kubectl run source-ip-app --image=k8s.gcr.io/echoserver:1.4
deployment "source-ip-app" created deployment.apps/source-ip-app created
``` ```
{{% /capture %}} {{% /capture %}}
@@ -60,10 +60,10 @@ a `proxyMode` endpoint:
```console ```console
$ kubectl get nodes $ kubectl get nodes
NAME STATUS AGE VERSION NAME STATUS ROLES AGE VERSION
kubernetes-minion-group-6jst Ready 2h v1.6.0+fff5156 kubernetes-minion-group-6jst Ready <none> 2h v1.11.1
kubernetes-minion-group-cx31 Ready 2h v1.6.0+fff5156 kubernetes-minion-group-cx31 Ready <none> 2h v1.11.1
kubernetes-minion-group-jj1t Ready 2h v1.6.0+fff5156 kubernetes-minion-group-jj1t Ready <none> 2h v1.11.1
kubernetes-minion-group-6jst $ curl localhost:10249/proxyMode kubernetes-minion-group-6jst $ curl localhost:10249/proxyMode
iptables iptables
@@ -73,11 +73,11 @@ You can test source IP preservation by creating a Service over the source IP app
```console ```console
$ kubectl expose deployment source-ip-app --name=clusterip --port=80 --target-port=8080 $ kubectl expose deployment source-ip-app --name=clusterip --port=80 --target-port=8080
service "clusterip" exposed service/clusterip exposed
$ kubectl get svc clusterip $ kubectl get svc clusterip
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
clusterip 10.0.170.92 <none> 80/TCP 51s clusterip ClusterIP 10.0.170.92 <none> 80/TCP 51s
``` ```
And hitting the `ClusterIP` from a pod in the same cluster: And hitting the `ClusterIP` from a pod in the same cluster:
@@ -116,7 +116,7 @@ are source NAT'd by default. You can test this by creating a `NodePort` Service:
```console ```console
$ kubectl expose deployment source-ip-app --name=nodeport --port=80 --target-port=8080 --type=NodePort $ kubectl expose deployment source-ip-app --name=nodeport --port=80 --target-port=8080 --type=NodePort
service "nodeport" exposed service/nodeport exposed
$ NODEPORT=$(kubectl get -o jsonpath="{.spec.ports[0].nodePort}" services nodeport) $ NODEPORT=$(kubectl get -o jsonpath="{.spec.ports[0].nodePort}" services nodeport)
$ NODES=$(kubectl get nodes -o jsonpath='{ $.items[*].status.addresses[?(@.type=="ExternalIP")].address }') $ NODES=$(kubectl get nodes -o jsonpath='{ $.items[*].status.addresses[?(@.type=="ExternalIP")].address }')
@@ -171,7 +171,7 @@ Set the `service.spec.externalTrafficPolicy` field as follows:
```console ```console
$ kubectl patch svc nodeport -p '{"spec":{"externalTrafficPolicy":"Local"}}' $ kubectl patch svc nodeport -p '{"spec":{"externalTrafficPolicy":"Local"}}'
service "nodeport" patched service/nodeport patched
``` ```
Now, re-run the test: Now, re-run the test:
@@ -220,11 +220,11 @@ You can test this by exposing the source-ip-app through a loadbalancer
```console ```console
$ kubectl expose deployment source-ip-app --name=loadbalancer --port=80 --target-port=8080 --type=LoadBalancer $ kubectl expose deployment source-ip-app --name=loadbalancer --port=80 --target-port=8080 --type=LoadBalancer
service "loadbalancer" exposed service/loadbalancer exposed
$ kubectl get svc loadbalancer $ kubectl get svc loadbalancer
NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
loadbalancer 10.0.65.118 104.198.149.140 80/TCP 5m loadbalancer LoadBalancer 10.0.65.118 104.198.149.140 80/TCP 5m
$ curl 104.198.149.140 $ curl 104.198.149.140
CLIENT VALUES: CLIENT VALUES: