This is the third step of running Kubernetes on AWS. We're ready to launch the Kubernetes cluster.
Now for the exciting part, creating your cluster:
$ kube-aws up --s3-uri s3://<your-bucket-name>/<prefix>
NOTE: It can take some time after
kube-aws up completes before the cluster is available. When the cluster is first being launched, it must download all container images for the cluster components (Kubernetes, dns, heapster, etc). Depending on the speed of your connection, it can take a few minutes before the Kubernetes api-server is available.
If you configured Route 53 settings in your configuration above via
createRecordSet, a host record has already been created for you.
Otherwise, navigate to the DNS registrar hosting the zone for the provided external DNS name. Ensure a single A record exists, routing the value of
externalDNSName defined in
cluster.yaml to the externally-accessible IP of the master node instance.
You can invoke
kube-aws status to get the cluster API endpoint after cluster creation, if necessary. This command can take a while.
A kubectl config file will be written to a
kubeconfig file, which can be used to interact with your Kubernetes cluster like so:
$ kubectl --kubeconfig=kubeconfig get nodes
If the container images are still downloading and/or the API server isn't accessible yet, the kubectl command above may show output similar to:
The connection to the server <externalDNSName>:443 was refused - did you specify the right host or port?
Wait a few more minutes for everything to complete.
Once the API server is running, you should see:
$ kubectl --kubeconfig=kubeconfig get nodes NAME STATUS AGE ip-10-0-0-xxx.us-west-1.compute.internal Ready 5m ip-10-0-0-xxx.us-west-1.compute.internal Ready 5m ip-10-0-0-xx.us-west-1.compute.internal Ready,SchedulingDisabled 5m
You're all done! The cluster is ready to use.
For full lifecycle information, read on below.
If you want to share, audit or back up your stack, use the export flag:
$ kube-aws up --export
Once you have successfully launched your cluster, you are ready to update your cluster.