1.9 KiB

Raw Blame History

*** PLEASE NOTE: This document applies to the HEAD of the source tree only. If you are using a released version of Kubernetes, you almost certainly want the docs that go with that version.

Documentation for specific releases can be found at releases.k8s.io.

Testing your Kubernetes cluster.

To validate that your node(s) have been added, run:

kubectl get nodes

That should show something like:

NAME           LABELS                                 STATUS
10.240.99.26   kubernetes.io/hostname=10.240.99.26    Ready
127.0.0.1      kubernetes.io/hostname=127.0.0.1       Ready

If the status of any node is Unknown or NotReady your cluster is broken, double check that all containers are running properly, and if all else fails, contact us on IRC at #google-containers for advice.

Run an application

kubectl -s http://localhost:8080 run nginx --image=nginx --port=80

now run docker ps you should see nginx running. You may need to wait a few minutes for the image to get pulled.

Expose it as a service:

kubectl expose rc nginx --port=80

This should print:

NAME      LABELS    SELECTOR              IP          PORT(S)
nginx     <none>    run=nginx             <ip-addr>   80/TCP

Hit the webserver:

curl <insert-ip-from-above-here>

Note that you will need run this curl command on your boot2docker VM if you are running on OS X.

Scaling

Now try to scale up the nginx you created before:

kubectl scale rc nginx --replicas=3

And list the pods

kubectl get pods

You should see pods landing on the newly added machine.

1.9 KiB Raw Blame History