whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Change RC to deployments in multi-container and simple-nginx docs

Browse Source
This commit is contained in:
Janet Kuo
2016-05-12 15:35:22 -07:00
parent 7edbc5f944
commit ded5417580
2 changed files with 17 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/user-guide/simple-nginx.md
+9 -7
View File
@@ -9,7 +9,9 @@ to Kubernetes and running your first containers on the cluster.
From this point onwards, it is assumed that `kubectl` is on your path from one of the getting started guides.
The [`kubectl run`](/docs/user-guide/kubectl/kubectl_run) line below will create two [nginx](https://registry.hub.docker.com/_/nginx/) [pods](/docs/user-guide/pods) listening on port 80. It will also create a [replication controller](/docs/user-guide/replication-controller) named `my-nginx` to ensure that there are always two pods running.
The [`kubectl run`](/docs/user-guide/kubectl/kubectl_run) line below will create a [`Deployment`](/docs/user-guide/deployments) named `my-nginx`, and
two [nginx](https://registry.hub.docker.com/_/nginx/) [pods](/docs/user-guide/pods) listening on port 80. The `Deployment` will ensure that there are
always exactly two pod running as specified in its spec.
```shell
kubectl run my-nginx --image=nginx --replicas=2 --port=80
@@ -21,16 +23,16 @@ Once the pods are created, you can list them to see what is up and running:
kubectl get pods
```
You can also see the replication controller that was created:
You can also see the Deployment that was created:
```shell
kubectl get rc
kubectl get deployments
```
To stop the two replicated containers, delete the replication controller:
To stop the two replicated containers, delete the Deployment:
```shell
kubectl delete rc my-nginx
kubectl delete deployment my-nginx
```
### Exposing your pods to the internet.
@@ -39,7 +41,7 @@ On some platforms (for example Google Compute Engine) the kubectl command can in
to do this run:
```shell
kubectl expose rc my-nginx --port=80 --type=LoadBalancer
kubectl expose deployment my-nginx --port=80 --type=LoadBalancer
```
This should print the service that has been created, and map an external IP address to the service. Where to find this external IP address will depend on the environment you run in. For instance, for Google Compute Engine the external IP address is listed as part of the newly created service and can be retrieved by running
@@ -53,4 +55,4 @@ In order to access your nginx landing page, you also have to make sure that traf
### Next: Configuration files
Most people will eventually want to use declarative configuration files for creating/modifying their applications. A [simplified introduction](/docs/user-guide/deploying-applications/)
is given in a different document.
is given in a different document.