I'm looking to get minikube working with either my custom docker macvlan network or a similar macvtap network for a KVM guest.

 

Out of the box minikube works with either the docker or kvm drivers but the default network makes the dashboard inaccessible.  Has anyone had any success at this?

 

I've tried specifying custom network parameters but it would seem minikube isn't happy with them and ignores them and creates its own

 

I've seen the other post here in this forum with a guide on this but thats not a direction I want to take ideally given its manual setup of KVM guests.

 

Any insight would be appreciated.

***Health warning*** I'm still learning k8s so there may be concerns with my solution. 

 

My reasons for doing this were to get away from using minikube on my Windows workstation, the course I was following was written for linux hosts and I was fed up with having to hack around the material to work in Windows.  I had my unraid server with both docker and kvm enabled so I wanted to be able to follow the courseware using that.

 

So after lots of failed attempts and reading I gave up with attempting to get minikube to use a macvtap network, I don't believe its possible by design.  Instead I focused on how to get the dashboard accessible via the bridge networks using minikubes docker or kvm2 driver.

 

Start minikube on the unraid server as normal (--force needed as unraid is root by default which minikube complains about):

minikube start --force --driver=docker

 

We cannot use the minikube binary to invoke the dashboard as there is no way I've found to enable remote access/get the local proxy instance listening to anything other than 127.0.01.  So to bypass minikuke first manually enable the needed addons:

minikube addons enable dashboard
minikube addons enable metrics-server

 

To then get to the k8s web dashboard from a remote client, instead of running 'minikube --dashboard' use:

kubectl proxy --address=0.0.0.0 --port=freeport --accept-hosts='.*'

This does allow you to configure the proxy to accept remote connections (--address=0.0.0.0) and means the dashboard url (http://unraid-server-ip:freeport/api/v1/namespaces/kubernetes-dashboard/services/http:kubernetes-dashboard:/proxy/) will now work with clients on your local subnet.

Edited November 4, 20241 yr by KillerK