mylesagray / blog-comments

Comments for Blah, Cloud. Hugo blog

0 stars 0 forks source link

Setting up K8s and the vSphere Cloud Provider using kubeadm | Blah, Cloud #56

Open utterances-bot opened 2 years ago

utterances-bot commented 2 years ago

Setting up K8s and the vSphere Cloud Provider using kubeadm | Blah, Cloud

How to enable the vSphere Cloud Provider with kubeadm

https://blah.cloud/kubernetes/setting-up-k8s-and-the-vsphere-cloud-provider-using-kubeadm/

CrimsonKidA commented 2 years ago

Hi Miles, Thanks for the great tutorial here! I'm trying this in June of 2022 and it seems there is a Docker issue with Ubuntu 18: https://stackoverflow.com/questions/48609712/failed-to-connect-to-containerd-failed-to-dial

I'm trying to upgrade them to Ubuntu 20 to see if that's the fix.

mylesagray commented 2 years ago

I couldn’t recommend following this nowadays 😊

The VCP is deprecated and due for removal from K8s core, maybe try out the newer guides based on the vSphere CSI or Cluster API?

CrimsonKidA commented 2 years ago

Got the docker / kubeadm issue sorted. Any ideas on this?

root@k8s-master:~# kubeadm init --config /etc/kubernetes/kubeadminitmaster.yaml --v=5 I0621 22:03:47.218322 11679 initconfiguration.go:255] loading configuration from "/etc/kubernetes/kubeadminitmaster.yaml" could not interpret GroupVersionKind; unmarshal error: error converting YAML to JSON: yaml: line 2: mapping values are not allowed in this context

CrimsonKidA commented 2 years ago

...never mind that last comment, got it now. This line was confusing me: sudo tee /etc/kubernetes/kubeadminitmaster.yaml >/dev/null <<EOF

Just copying/pasting your entire block created the kubeadminitmaster.yaml file with the proper formatting for me. :)