From 8c4fc0351ac5fa4b0f396b7c1c17b43e0ecb54f4 Mon Sep 17 00:00:00 2001 From: Chris Riviere Date: Mon, 21 Nov 2016 11:27:15 -0800 Subject: [PATCH 1/5] 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 From 08577c385a27a32056c876307986428689f9e6b9 Mon Sep 17 00:00:00 2001 From: Chris Riviere Date: Mon, 21 Nov 2016 12:08:25 -0800 Subject: [PATCH 2/5] minor changes moved text under command and changed wording based on some feedback. With regards to mentioning cloud providers. I think a lot of this documentation in general assumes a public cloud like Google so it may be worthwhile to mention a specific private cloud where this isn't implemented. --- docs/user-guide/quick-start.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/user-guide/quick-start.md b/docs/user-guide/quick-start.md index fcb3b079b9..6e0920f973 100644 --- a/docs/user-guide/quick-start.md +++ b/docs/user-guide/quick-start.md @@ -22,12 +22,13 @@ $ kubectl run my-nginx --image=nginx --replicas=2 --port=80 deployment "my-nginx" created ``` -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). +To expose your service to the public internet, run the following: ```shell $ kubectl expose deployment my-nginx --target-port=80 --type=LoadBalancer service "my-nginx" exposed ``` +Note: The type, LoadBalancer, is highly dependant upon the underlying platform that Kubernetes is running on. If your cloudprovider doesn't have a loadbalancer implementation (e.g. OpenStack) for Kubernetes, you can simply use the allocated [nodePort](link to nodeport service) as a rudimentary form of loadblancing across your endpoints. You can see that they are running by: From 18068bae8037d5c0f4779c7133fc3edfc5595585 Mon Sep 17 00:00:00 2001 From: Chris Riviere Date: Mon, 21 Nov 2016 12:09:05 -0800 Subject: [PATCH 3/5] minor text change --- 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 6e0920f973..0cf35997b4 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 the following: +To expose your service to the public internet, run: ```shell $ kubectl expose deployment my-nginx --target-port=80 --type=LoadBalancer From e73c755de32eac119a5828c922b1e584cb00f06b Mon Sep 17 00:00:00 2001 From: Anirudh Ramanathan Date: Mon, 21 Nov 2016 13:11:19 -0800 Subject: [PATCH 4/5] Updated link and fixed typo --- 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 0cf35997b4..e64f9d1d19 100644 --- a/docs/user-guide/quick-start.md +++ b/docs/user-guide/quick-start.md @@ -28,7 +28,7 @@ To expose your service to the public internet, run: $ kubectl expose deployment my-nginx --target-port=80 --type=LoadBalancer service "my-nginx" exposed ``` -Note: The type, LoadBalancer, is highly dependant upon the underlying platform that Kubernetes is running on. If your cloudprovider doesn't have a loadbalancer implementation (e.g. OpenStack) for Kubernetes, you can simply use the allocated [nodePort](link to nodeport service) as a rudimentary form of loadblancing across your endpoints. +Note: The type, LoadBalancer, is highly dependent upon the underlying platform that Kubernetes is running on. If your cloudprovider doesn't have a loadbalancer implementation (e.g. OpenStack) for Kubernetes, you can simply use the allocated [NodePort](http://kubernetes.io/docs/user-guide/services/#type-nodeport) as a rudimentary form of loadblancing across your endpoints. You can see that they are running by: From 58822257f0bef0838a7e7ba90dd93b5de40c05d9 Mon Sep 17 00:00:00 2001 From: devin-donnelly Date: Wed, 21 Dec 2016 16:15:24 -0800 Subject: [PATCH 5/5] Update quick-start.md --- 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 e64f9d1d19..7fc3c3faa1 100644 --- a/docs/user-guide/quick-start.md +++ b/docs/user-guide/quick-start.md @@ -28,7 +28,7 @@ To expose your service to the public internet, run: $ kubectl expose deployment my-nginx --target-port=80 --type=LoadBalancer service "my-nginx" exposed ``` -Note: The type, LoadBalancer, is highly dependent upon the underlying platform that Kubernetes is running on. If your cloudprovider doesn't have a loadbalancer implementation (e.g. OpenStack) for Kubernetes, you can simply use the allocated [NodePort](http://kubernetes.io/docs/user-guide/services/#type-nodeport) as a rudimentary form of loadblancing across your endpoints. +Note: The type, LoadBalancer, is highly dependent upon the underlying platform that Kubernetes is running on. If your cloud provider doesn't have a load balancer implementation (e.g. OpenStack) for Kubernetes, you can simply use the allocated [NodePort](http://kubernetes.io/docs/user-guide/services/#type-nodeport) as a rudimentary form of load balancing across your endpoints. You can see that they are running by: