github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #9007 from jeffmendoza/nginx-doc 

Clarify simple nginx example doc.
pull/6/head
Rohit Jnagal 2015-06-01 10:43:04 -07:00
parent ebd4506a59 8aea326b89
commit 2ffb875129
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
examples/simple-nginx.md
View File

@ -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