Questions[multipass](server)

I am thinking about using multiple microk8s nodes on MacOs M1. If I am using LXD I can have multiple VMs running microk8s in a virtuel cluster simulating one-n k8s nodes.

LXD looks very good for managing vm and system containers.

I found that LXD does not work on my MacOs M1 machine and I have to use a LXD server installed using multiples. Will this server then contain every vm that again contain microk8s?

My question is, should I just use multipass(LXD server) or/and wait for Will LXD 5.0 LTS?

I am trying to add storage to an existing Multipass VM. I created a new ZFS filesystem, mounted locally at /zfs/morespace. Then tried to mount it with

multipass mount /zfs/morespace existingvm:/mnt/morespace

I received the error:

Source path "/zfs/morespace" does not exist

When I ls /zfs "morespace" is listed.
I also created a folder /zfs/morespace/storagedir and tried to mount that with the same result.

Can anyone help me understand why Multipass cannot find the zfs file system or directories inside of it, while ubuntu has no issue? Most of my storage is on a large zpool with multiple zfs file systems, and I would like to be able to utilize this for extra VM storage, without having to resize the system images.

I have several multipass instances running in an Ubuntu 18 environment. These are webservers for development and should be accessible in my local network. To allow connections from other computers on the network I used iptables to change the default FORWARD rule

ACCEPT     all  --  anywhere             10.54.188.0/24       ctstate RELATED,ESTABLISHED

to

ACCEPT     all  --  anywhere             10.54.188.0/24

That allows all incoming connections to be routed to the multipass instances. The problem came up the other day, when it appears multipass daemon restarted and overwrote my modified iptables rule (2nd rule above) with the default rule (top rule above).

How can I modify the multipass default iptables rules so any time the daemon reloads, or on a server restart I don't have to manually update the iptables rules again?

I want to setup a local Kubernetes cluster for testing on macOS. I selected microk8s provided by Canonical. Kubernetes doesn't run native on macOS, but uses a Linux VM provided by multipass.

Installation was smooth and deployment of the kubernetes-bootcamp seemed to have worked. This is the output I got so far:

microk8s kubectl get services

NAME                  TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)          AGE
kubernetes            ClusterIP   10.152.183.1     <none>        443/TCP          5h9m
kubernetes-bootcamp   NodePort    10.152.183.226   <none>        8080:31004/TCP   4h10m

multipass list

Name                    State             IPv4             Image
microk8s-vm             Running           192.168.64.2     Ubuntu 18.04 LTS

Pinging the instance with ping 192.168.64.2 works as expected.

Update: I further tested connectivity by installing nginx inside the VM. Using curl http://192.168.64.2 the nginx startpage inside the VM showed up on macOS.

Now when I shell into the VM using multipass exec microk8s-vm -- bash, I can curl into my deployed service as expected with both:

• curl http://127.0.0.1:31004
• curl http://10.152.183.226:8080

Getting the expected result of:

Hello Kubernetes bootcamp! | Running on: kubernetes-bootcamp-57978f5f5d-d977w | v=1

However I'm missing the step to access these url from macOS (both curl and a browser). I tried unsuccessfully:

• curl http://10.152.183.226:8080
• curl http://10.152.183.226:31004
• curl http://192.168.64.2:8080
• curl http://192.168.64.2:31004

I'm obviously missing a step to make the running services accessible from the macOS host. What did I miss? Help is very much appreciated!