I was pretty stoked to setup a Kubernetes cluster on Virtualbox this weekend. I followed this video to setup the cluster. I don’t understand 100% of what I did but I got it up and running…so that’s a start.
I’ve noted some differences with what was being described in the video and what I had to do in order to get the cluster running.
7:00 – In Virtualbox, the location is now File | Tools | Network Manager
18:31 – I was getting an error for the repository “…Kubernetes-xenial Release” does not have a release file.
I found this URL with replies by chrispokorni: https://forum.linuxfoundation.org/discussion/864693/the-repository-http-apt-kubernetes-io-kubernetes-xenial-release-does-not-have-a-release-file
He says to do the following commands:
curl -fsSL https://pkgs.k8s.io/core:/stable:/v1.28/deb/Release.key | sudo gpg --dearmor -o /etc/apt/keyrings/kubernetes-apt-keyring.gpgecho 'deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v1.28/deb/ /' | sudo tee /etc/apt/sources.list.d/kubernetes.listsudo apt updatesudo apt install -y kubeadm=1.28.1-1.1 kubelet=1.28.1-1.1 kubectl=1.28.1-1.1(I wanted 1.29, which seems to be the latest, so I just replaced all references to 1.28 with 1.29)
23:39 – The URL for Project Calico YAML is actually https://calico-v3-25.netlify.app/archive/v3.25/manifests/calico.yaml
31:43 – I found the following URL with replies by TheDHM after having some trouble with the taint command: https://stackoverflow.com/questions/43147941/allow-scheduling-of-pods-on-kubernetes-master
The command to taint the master node is: kubectl taint node —all node-role.kubernetes.io/control-plane:NoSchedule-