Summary

In this chapter, we looked at four cloud providers. The first two, DigitalOcean and AWS, at present do not natively support Kubernetes so we used kubeadm and kube-aws to launch and configure our clusters. With Microsoft Azure and Google Cloud we used their command-line tools to launch their natively supported Kubernetes services. I am sure you will agree that at the time of writing both of these services are a lot friendlier to use than the first two we looked at.

Once the clusters were up-and-running, interacting with Kubernetes was a pretty consistent experience. We didn't really have to make allowances for where our cluster was running when issuing commands such as kubectl expose: Kubernetes was aware of where it was running and used the provider's native services to launch a Load Balancer without us have to intervene with any special settings or considerations.

You may be wondering why we didn't launch the Sock Shop application on DigitalOcean. As the spec of the machines was quite...