-1

I am in front of a book to teaching myself Kubernetes.

It has many chapters about handling a Kubernetes cluster, and it urges the reader to create an account on a cloud server, if he can. Else to attempt creating a cluster of few Raspberry Pi. But I don't want or cannot afford these choices. I have my own home computer, that's all.

Is it something that prevents me from creating a multi-machine Vagrant to create all computers my book could talk about?
I believe this could work...

My question is simple and naive. But if there's an obstacle or a big difficulty that I will surely face, I'd like to know it immediately before choosing this wrong way. Thanks!

Improve this question
6
  • Why not microk8s or minikube? Commented Apr 17 at 16:25
  • Google Free Kubernetes Or go watch Network Chuck's YouTube channel. Using the affiliate link for some of his Kubernetes videos give you a free cluster for a month. Just be sure to cancel before month's end. Commented Apr 17 at 16:27
  • How many clusters do you need? Commented Apr 17 at 16:28
  • @muru I don't know yet. It will be known and surely variable depending on the chapters content. Commented Apr 17 at 16:31
  • @muru The book says : "minikube creates only a cluster with an unique node, that cannot allow to demonstrate all the Kubernetes capacities". My book strongly suggest to make another choice than minikube. Commented Apr 17 at 17:50

1 Answer 1

Reset to default
3

Yeah, sure; a bunch of VMs is usually how you learn these kinds of technologies. Vagrant is a quick way to pull up a couple of clones of the same VM. And, yeah, running this as VMs on your machine sounds much more sensible than doing it on many RPis.

Give them all their own (virtual) network interface, attached to the same network bridge device, so they can talk among themselves.

But honestly, minikube does something very similar. I don't see any restrictions of that which would become relevant to you anytime soon. You claim in the comments that minicube can only spawn a single cluster, but that's not correct. You can spawn as many clusters as you need. But generally, you'll work on one cluster with multiple VMs.

Improve this answer
6
  • The book says: "minikube creates only a cluster with an unique node, that cannot allow to demonstrate all the Kubernetes capacities" Commented Apr 17 at 17:49
  • well, that's wrong. You can make minikube set up as many clusters as you want, and they can have as many nodes as they want; minikube start --nodes {N}. By the way, something that you could have researched yourself after I have already told you your book is wrong about it. Commented Apr 17 at 18:07
  • Muller I'll try to stay with minikube until the very moment where something will force me to use a multi-machine VM instead. If it happens, I'll try to remember to write here what will have forced that. Your advice, of all of you, are good ones and are useful. Thanks! Commented Apr 17 at 18:19
  • again, minikube can create multi-machine clusters, no problem. And it can create as many clusters as you want. You're seeing problems where there arent't any, Commented Apr 17 at 18:27
  • @MarcLeBihan is it possible your book was written some time ago, and minikube has gained more functionality since then? Technology often changes faster than publishing. Commented Apr 18 at 5:17

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.