From 8c4fc0351ac5fa4b0f396b7c1c17b43e0ecb54f4 Mon Sep 17 00:00:00 2001 From: Chris Riviere Date: Mon, 21 Nov 2016 11:27:15 -0800 Subject: [PATCH] clarification on type LoadBalancer for exposing Took me a bit of time to learn that type LadBalancer wasn't fully working in an OpenStack environment as I was going through this. --- docs/user-guide/quick-start.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/quick-start.md b/docs/user-guide/quick-start.md index 9e9e59dbd8..fcb3b079b9 100644 --- a/docs/user-guide/quick-start.md +++ b/docs/user-guide/quick-start.md @@ -22,7 +22,7 @@ $ kubectl run my-nginx --image=nginx --replicas=2 --port=80 deployment "my-nginx" created ``` -To expose your service to the public internet, run: +To expose your service to the public internet, run the following. Note, the type, LoadBalancer, is highly dependant upon the underlying platform that Kubernetes is running on. Type LoadBalancer may work in public cloud environments just fine but may require some additional configuration in a private cloud environment (ie. OpenStack). ```shell $ kubectl expose deployment my-nginx --target-port=80 --type=LoadBalancer