From 541e6d5538a040c4e94e4b5e75498d9ce0c0e5d1 Mon Sep 17 00:00:00 2001 From: Jacob Tomlinson Date: Tue, 21 Jul 2015 15:03:21 +0100 Subject: [PATCH] Fixed command --- 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 5b321058b87..0f3bd2175b9 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",