To switch between network modes go to menu bar when virtual machine is active > Devices menu > Network. To uninstall your cluster use the following command /usr/local/bin/k3s-uninstall.Virtual machine can use three different networking modes depending on user needs:

Here a subfolder is created for every local-path PersistentVolumeClaim. You can find it in the /var/lib/rancher/k3s/storage folder. The local-path storage class, what’s in a name, stores the data of the volume on a directory of the host, our Ubuntu VM in this case. This is the volume PersistentVolumeClaim I’m using for my MongoDB instance. See the following PersistentVolumeClaim for an example how to use it. k3s supports the local-path storage class out of the box. If you want the data of your pods to survive a restart or reboot using a persistent volume is the way to go. This means that I can connect directly to ports on my VM to interact with the services I deployed in the cluster, which I need for my local development workflow. The beauty of this setup is that all services that are exposed using NodePort are available directly on the host (the Ubuntu VM). Now you can use kubectl to interact with the k3s cluster. sudo cp /etc/rancher/k3s/k3s.* $HOME/.kube/config Depending on your setup you might need to copy the kube config of k3s to the ~/.kube/config file. kube-apiserver-arg service-node-port-range=1-65535 I’ve added an additional argument that allows services to expose themselves at any port (by default this is restricted to the 30000-32768 range).

When the Ubuntu VM is up and running launch a terminal to install k3s. After installing, launch the Ubuntu VM suggested in the dialog. Here are the steps.įirst of all download and install Parallels Desktop. As k3s doesn’t need docker it sounds like an attractive alternative. This time I installed k3s on a Ubuntu virtual machine running in Parallels Desktop. In my search for the ideal k8s setup on a M1 mac I tried an alternative approach. It’s not very often, but annoying enough to give this alternative a try. This approach has some downsides, the first being the need for port forwards, second minikube and multipass sometimes display some quirky behaviour. In my previous post I described how to get a minikube cluster up and running using multipass.

Ubuntu m1 parallels