From 8aea326b897521eec18970c37bc92f523e6a1124 Mon Sep 17 00:00:00 2001 From: Jeff Mendoza Date: Fri, 29 May 2015 09:35:10 -0700 Subject: [PATCH] Clarify simple nginx example doc. --- examples/simple-nginx.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/examples/simple-nginx.md b/examples/simple-nginx.md index 254856d9bf..d90e780618 100644 --- a/examples/simple-nginx.md +++ b/examples/simple-nginx.md @@ -6,10 +6,9 @@ to Kubernetes and running your first containers on the cluster. ### Running a container (simple version) -From this point onwards, it is assumed that ```kubectl``` is on your path from one of the getting started guides. +From this point onwards, it is assumed that `kubectl` is on your path from one of the getting started guides. -The `kubectl` line below spins up two containers running -[Nginx](http://nginx.org/en/) running on port 80: +The [`kubectl run`](/docs/kubectl_run.md) line below will create two [nginx](https://registry.hub.docker.com/_/nginx/) [pods](/docs/pods.md) listening on port 80. It will also create a [replication controller](/docs/replication-controller.md) named `my-nginx` to ensure that there are always two pods running. ```bash kubectl run my-nginx --image=nginx --replicas=2 --port=80 @@ -31,7 +30,7 @@ kubectl stop rc my-nginx ``` ### Exposing your pods to the internet. -On some platforms (for example Google Compute Engine) the kubectl command can integrate with your cloud provider to add a public IP address for the pods, +On some platforms (for example Google Compute Engine) the kubectl command can integrate with your cloud provider to add a [public IP address](/docs/services.md#external-services) for the pods, to do this run: ```bash