Tarpers (1) [Avatar] Offline
As an individual living in the EU, I found running the examples in the book using Google Container Engine prohibitive. This is because Google disuade private individuals from using the Cloud Platform in most of the EU due to EU tax rules (see https://support.google.com/cloud/answer/6090602?hl=en).

I tried to set up a cluster using Vagrant but hit some issues. While trying to resolve these issues, I noticed that creating a cluster using Vagrant has been deprecated (http://kubernetes.io/docs/getting-started-guides/alternatives/). The recommended method for running Kubernetes locally is now Minikube (http://kubernetes.io/docs/getting-started-guides/minikube/).

Minikube currently only runs a single node cluster but I was able to successfully run the examples in Chapter 2 using it.

Would it be worth mentioning Minikube in chapter 2 (possibly replacing the advice about Vagrant in section 2.2.1)?

Marko Lukša (6) [Avatar] Offline
Yes, I'm planning on adding a section detailing how to run a local single-node K8s setup with Minikube. Some reviewers disliked the fact you need to supply your credit card info to Google in order to use K8s on Google Container Engine.

450699 (1) [Avatar] Offline
What about the area in between "Full Google" (Google handles cluster complexity via GKE) and "Minikube" (There is no cluster complexity)? So far the book has had everything I need in a Kubernetes book except "How to deploy your own simple 3-node cluster". The Kuberenetes Docs do it here: https://kubernetes.io/docs/getting-started-guides/scratch but I'd love to be guided through it by an expert.

Just my thoughts. Thank you! Great book so far.
Marko Lukša (6) [Avatar] Offline
Thanks for the suggestion. My initial Table of Contents proposal actually included a section like this in Chapter 2, but I later realized it's probably unnecessary, since at that point of the book, the readers wouldn't know enough about the architecture and would also probably just want to start playing around with Kubernetes with the least effort required to set it up.

But I do agree this is something a lot of readers would find useful. I'm just not sure where exactly to put it. Chapter 2 seems much too early. Plus, using kubeadm makes it very simple and is well documented in the online documentation. Maybe I'll just mention kubeadm in Chapter 2 and leave it at that.

If you have additional suggestions, I'll be glad to hear them.