Skip to content

Latest commit

 

History

History
47 lines (33 loc) · 1.86 KB

simple-nginx.md

File metadata and controls

47 lines (33 loc) · 1.86 KB

Running your first containers in Kubernetes

Ok, you've run one of the getting started guides and you have successfully turned up a Kubernetes cluster. Now what? This guide will help you get oriented 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.

The kubectl run line below will create two nginx pods listening on port 80. It will also create a replication controller named my-nginx to ensure that there are always two pods running.

kubectl run my-nginx --image=nginx --replicas=2 --port=80

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:

kubectl get rc

To stop the two replicated containers, stop the replication controller:

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, to do this run:

kubectl expose rc my-nginx --port=80 --type=LoadBalancer

This should print the service that has been created, and map an external IP address to the service.

Next: Configuration files

Most people will eventually want to use declarative configuration files for creating/modifying their applications. A simplified introduction is given in a different document.

Analytics