From 9a010a71c8f272c3bbc863731e6181ac99f233e3 Mon Sep 17 00:00:00 2001 From: Morten Andersen Date: Wed, 29 Jul 2015 07:42:55 +0200 Subject: [PATCH 1/2] typo --- docs/user-guide/connecting-applications.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/connecting-applications.md b/docs/user-guide/connecting-applications.md index f2303419f73..d3fc200fd03 100644 --- a/docs/user-guide/connecting-applications.md +++ b/docs/user-guide/connecting-applications.md @@ -375,7 +375,7 @@ $ kubectl exec curlpod -- curl https://nginxsvc --cacert /etc/nginx/ssl/nginx.cr For some parts of your applications you may want to expose a Service onto an external IP address. Kubernetes supports two ways of doing this: NodePorts and LoadBalancers. The Service created in the last section already used `NodePort`, so your nginx https replica is ready to serve traffic on the internet if your node has a public IP. ```console -$ kubeclt get svc nginxsvc -o json | grep -i nodeport -C 5 +$ kubectl get svc nginxsvc -o json | grep -i nodeport -C 5 { "name": "http", "protocol": "TCP", From e8017d3a907b0098e59618dc88def3a883cfad7e Mon Sep 17 00:00:00 2001 From: Morten Andersen Date: Wed, 29 Jul 2015 07:50:05 +0200 Subject: [PATCH 2/2] Missing argument to get documented result --- docs/user-guide/connecting-applications.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/connecting-applications.md b/docs/user-guide/connecting-applications.md index d3fc200fd03..3aabeb265bc 100644 --- a/docs/user-guide/connecting-applications.md +++ b/docs/user-guide/connecting-applications.md @@ -391,7 +391,7 @@ $ kubectl get svc nginxsvc -o json | grep -i nodeport -C 5 "nodePort": 30645 } -$ kubectl get nodes -o json | grep ExternalIP +$ kubectl get nodes -o json | grep ExternalIP -C 2 { "type": "ExternalIP", "address": "104.197.63.17"