Fresh debian 10 vm - microk8s not starting properly

General Discussions microk8s
1

Hi,

I tried to setup microk8s on a fresh debian 9, didn’t work.
So I installed debian 10, set up both ipv4 and ipv6.
Installed microk8s 1.20.

microk8s starts but calico node dosn’t start properly

# microk8s kubectl --namespace=kube-system describe pod calico-node
...
Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
...
  Normal   Created    86s                kubelet            Created container calico-node
  Normal   Started    83s                kubelet            Started container calico-node
  Warning  Unhealthy  31s (x6 over 81s)  kubelet            Readiness probe failed: calico/node is not ready: felix is not ready: Get http://localhost:9099/readiness: dial tcp [::1]:9099: connect: connection refused
  Warning  Unhealthy  29s (x5 over 69s)  kubelet            Liveness probe failed: calico/node is not ready: Felix is not live: Get http://localhost:9099/liveness: dial tcp [::1]:9099: connect: connection refused

status of microk8s looks fine

# microk8s status
microk8s is running
high-availability: no
  datastore master nodes: 127.0.0.1:19001
  datastore standby nodes: none
addons:
  enabled:
    ha-cluster           # Configure high availability on the current node
  disabled:
    ...

so I tried inspect

# microk8s inspect
Inspecting Certificates
Inspecting services
  Service snap.microk8s.daemon-cluster-agent is running
  Service snap.microk8s.daemon-containerd is running
  Service snap.microk8s.daemon-apiserver is running
  Service snap.microk8s.daemon-apiserver-kicker is running
  Service snap.microk8s.daemon-control-plane-kicker is running
 FAIL:  Service snap.microk8s.daemon-proxy is not running
For more details look at: sudo journalctl -u snap.microk8s.daemon-proxy
  Service snap.microk8s.daemon-kubelet is running

so journalctl shows

Jan 20 22:54:21 v31 microk8s.daemon-proxy[8454]: + exec /snap/microk8s/1910/kube-proxy --kubeconfig=/var/snap/microk8s/1910/credentials/proxy.config --cluster-cidr=10.1.0.0/16 --healthz-bind-address=127.0.0.1
Jan 20 22:54:21 v31 microk8s.daemon-proxy[8454]: W0120 22:54:21.418847    8454 server.go:226] WARNING: all flags other than --config, --write-config-to, and --cleanup are deprecated. Please begin using a config file ASAP.
Jan 20 22:54:21 v31 microk8s.daemon-proxy[8454]: I0120 22:54:21.438767    8454 node.go:172] Successfully retrieved node IP: 2a01:4f8:191:4224::31
Jan 20 22:54:21 v31 microk8s.daemon-proxy[8454]: I0120 22:54:21.438797    8454 server_others.go:139] kube-proxy node IP is an IPv6 address (2a01:4f8:191:4224::31), assume IPv6 operation
Jan 20 22:54:21 v31 microk8s.daemon-proxy[8454]: W0120 22:54:21.440668    8454 server_others.go:578] Unknown proxy mode "", assuming iptables proxy
Jan 20 22:54:21 v31 microk8s.daemon-proxy[8454]: I0120 22:54:21.440859    8454 server_others.go:185] Using iptables Proxier.
Jan 20 22:54:21 v31 microk8s.daemon-proxy[8454]: F0120 22:54:21.440991    8454 server.go:495] unable to create proxier: CIDR 10.1.0.0/16 has incorrect IP version: expect isIPv6=true
Jan 20 22:54:21 v31 systemd[1]: snap.microk8s.daemon-proxy.service: Main process exited, code=exited, status=1/FAILURE
Jan 20 22:54:21 v31 systemd[1]: snap.microk8s.daemon-proxy.service: Failed with result 'exit-code'.

this is freshly installed, debian 10 is upgraded to the latest version, snap install went fine

This is where I’m stuck

hope the formatting worked

2

It seems like your network interface doesn’t have an ipv4. If you want ipv6 @reingart wrote a nice tutorial on how to make ipv6 work with MicroK8s here MicroK8s IPv6 DualStack HOW-TO

3

I do have ipv4 and ipv6 set up (on 2 different network interfaces) and using ssh to connect to either address works fine as well as curl -4 and curl -6 to access the internet.

So would it help to point it to use a different network interface? (using ipv4)
How would I do that?

I don’t need ipv6 at the moment und would rather get this working before doing fancy things like getting ipv4/6 dual stack online.

4

In my case i just turned off ipv6. :grinning:

5

turning off ipv6 helped and I got it running after solving a couple of minor issues