Networking microk8s following ubuntu tutorial

I’m following this tutorial https://tutorials.ubuntu.com/tutorial/install-a-local-kubernetes-with-microk8s#1

But is there a bridged network that gets created during the snap microk8s install cbr0. There isn’t any. `Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination
0 0 KUBE-PORTALS-CONTAINER all – * * 0.0.0.0/0 0.0.0.0/0 /* handle ClusterIPs; NOT E: this must be before the NodePort rules / 0 0 KUBE-NODEPORT-CONTAINER all – * * 0.0.0.0/0 0.0.0.0/0 ADDRTYPE match dst-type LOCAL / handle service NodePorts; NOTE: this must be the last rule in the chain */ 0 0 DOCKER all – * * 0.0.0.0/0 0.0.0.0/0 ADDRTYPE match dst-type LOCAL

Chain INPUT (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination
10072 595K KUBE-PORTALS-HOST all – * * 0.0.0.0/0 0.0.0.0/0 /* handle ClusterIPs; NOTE: th is must be before the NodePort rules / 9757 572K KUBE-NODEPORT-HOST all – * * 0.0.0.0/0 0.0.0.0/0 ADDRTYPE match dst-type LOCAL / handle service NodePorts; NOTE: this must be the last rule in the chain */ 0 0 DOCKER all – * * 0.0.0.0/0 !127.0.0.0/8 ADDRTYPE match dst-type LOCAL

Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination
369 22034 KUBE-POSTROUTING all – * * 0.0.0.0/0 0.0.0.0/0 /* kubernetes postrouting rules / 0 0 MASQUERADE all – * !docker0 172.17.0.0/16 0.0.0.0/0
250 18890 MASQUERADE all – * * 0.0.0.0/0 !10.152.183.0/24 / kubenet: SNAT for outbound traffic from cluster */ ADDRTYPE match dst-type !LOCAL

Chain DOCKER (2 references) pkts bytes target prot opt in out source destination
0 0 RETURN all – docker0 * 0.0.0.0/0 0.0.0.0/0

Chain KUBE-MARK-DROP (0 references) pkts bytes target prot opt in out source destination
0 0 MARK all – * * 0.0.0.0/0 0.0.0.0/0 MARK or 0x8000

Chain KUBE-MARK-MASQ (0 references) pkts bytes target prot opt in out source destination
0 0 MARK all – * * 0.0.0.0/0 0.0.0.0/0 MARK or 0x4000

Chain KUBE-NODEPORT-CONTAINER (1 references) pkts bytes target prot opt in out source destination

Chain KUBE-NODEPORT-HOST (1 references) pkts bytes target prot opt in out source destination

Chain KUBE-PORTALS-CONTAINER (1 references) pkts bytes target prot opt in out source destination
0 0 REDIRECT tcp – * * 0.0.0.0/0 10.152.183.1 /* default/kubernetes:https / tcp dpt :443 redir ports 38715 0 0 REDIRECT tcp – * * 0.0.0.0/0 10.152.183.56 / kube-system/kubernetes-dashboard: * / tcp dpt:443 redir ports 40565 0 0 REDIRECT tcp – * * 0.0.0.0/0 10.152.183.70 /* kube-system/monitoring-grafana: / tcp dpt:80 redir ports 45491 0 0 REDIRECT tcp – * * 0.0.0.0/0 10.152.183.201 / kube-system/monitoring-influxdb:htt p / tcp dpt:8083 redir ports 45709 0 0 REDIRECT tcp – * * 0.0.0.0/0 10.152.183.201 / kube-system/monitoring-influxdb:api / tcp dpt:8086 redir ports 41271 0 0 REDIRECT tcp – * * 0.0.0.0/0 10.152.183.184 / kube-system/heapster: */ tcp dpt:80 redir ports 45569

Chain KUBE-PORTALS-HOST (1 references) pkts bytes target prot opt in out source destination
0 0 DNAT tcp – * * 0.0.0.0/0 10.152.183.1 /* default/kubernetes:https / tcp dpt:443 to:192.168.3.100:38715 0 0 DNAT tcp – * * 0.0.0.0/0 10.152.183.56 / kube-system/kubernetes-dashboard: / tcp dpt:443 to:192.168.3.100:40565 0 0 DNAT tcp – * * 0.0.0.0/0 10.152.183.70 / kube-system/monitoring-grafana: / tcp dpt:80 to:192.168.3.100:45491 0 0 DNAT tcp – * * 0.0.0.0/0 10.152.183.201 / kube-system/monitoring-influxdb:http / tcp dpt:8083 to:192.168.3.100:45709 0 0 DNAT tcp – * * 0.0.0.0/0 10.152.183.201 / kube-system/monitoring-influxdb:api / tcp dpt:8086 to:192.168.3.100:41271 0 0 DNAT tcp – * * 0.0.0.0/0 10.152.183.184 / kube-system/heapster: */ tcp dpt:80 to:192.168.3.100:45569

Chain KUBE-POSTROUTING (1 references) pkts bytes target prot opt in out source destination
0 0 MASQUERADE all – * * 0.0.0.0/0 0.0.0.0/0 /* kubernetes service traffic requiring SNAT */ mark match 0x4000/0x4000 ` Are these rules conflicting with previous firewall forwarding rules set by docker? Also I’ve got these messages in the logs

’ Mar 01 13:11:08 ubs microk8s.daemon-proxy[4966]: W0301 13:11:08.811303 4966 server.go:194] WARNING: all flags other than --config, --write-config-to, and --cleanup are deprecated. Please begin using a config file ASAP. Mar 01 13:11:09 ubs microk8s.daemon-proxy[4966]: W0301 13:11:09.010578 4966 node.go:103] Failed to retrieve node info: Get http://127.0.0.1:8080/api/v1/nodes/ubs: dial tcp 127.0.0.1:8080: connect: connection refused Mar 01 13:11:09 ubs microk8s.daemon-proxy[4966]: I0301 13:11:09.010631 4966 server_others.go:221] Using userspace Proxier. Mar 01 13:11:09 ubs microk8s.daemon-proxy[4966]: I0301 13:11:09.052922 4966 server_others.go:247] Tearing down inactive rules. Mar 01 13:11:09 ubs microk8s.daemon-proxy[4966]: E0301 13:11:09.062576 4966 proxier.go:395] Error removing pure-iptables proxy rule: error checking rule: exit status 2: iptables v1.6.1: Couldn’t find target KUBE-EXTERNAL-SERVICES' Mar 01 13:11:09 ubs microk8s.daemon-proxy[4966]: Try iptables -h’ or ‘iptables --help’ for more information. Mar 01 13:11:09 ubs microk8s.daemon-proxy[4966]: E0301 13:11:09.064993 4966 proxier.go:395] Error removing pure-iptables proxy rule: error checking rule: exit status 2: iptables v1.6.1: Couldn’t find target KUBE-SERVICES' Mar 01 13:11:09 ubs microk8s.daemon-proxy[4966]: Try iptables -h’ or ‘iptables --help’ for more information. Mar 01 13:11:09 ubs microk8s.daemon-proxy[4966]: E0301 13:11:09.066967 4966 proxier.go:395] Error removing pure-iptables proxy rule: error checking rule: exit status 2: iptables v1.6.1: Couldn’t find target KUBE-SERVICES' Mar 01 13:11:09 ubs microk8s.daemon-proxy[4966]: Try iptables -h’ or ‘iptables --help’ for more information. Mar 01 13:11:09 ubs microk8s.daemon-proxy[4966]: E0301 13:11:09.069172 4966 proxier.go:395] Error removing pure-iptables proxy rule: error checking rule: exit status 2: iptables v1.6.1: Couldn’t find target KUBE-SERVICES' Mar 01 13:11:09 ubs microk8s.daemon-proxy[4966]: Try iptables -h’ or ‘iptables --help’ for more information. Mar 01 13:11:09 ubs microk8s.daemon-proxy[4966]: E0301 13:11:09.073988 4966 proxier.go:395] Error removing pure-iptables proxy rule: error checking rule: exit status 2: iptables v1.6.1: Couldn’t find target KUBE-FORWARD' Mar 01 13:11:09 ubs microk8s.daemon-proxy[4966]: Try iptables -h’ or ‘iptables --help’ for more information. Mar 01 13:11:09 ubs microk8s.daemon-proxy[4966]: E0301 13:11:09.076076 4966 proxier.go:395] Error removing pure-iptables proxy rule: error checking rule: exit status 2: iptables v1.6.1: Couldn’t find target KUBE-SERVICES' Mar 01 13:11:09 ubs microk8s.daemon-proxy[4966]: Try iptables -h’ or ‘iptables --help’ for more information. Mar 01 13:11:09 ubs microk8s.daemon-proxy[4966]: E0301 13:11:09.078144 4966 proxier.go:395] Error removing pure-iptables proxy rule: error checking rule: exit status 2: iptables v1.6.1: Couldn’t find target `KUBE-SERVICES’

’ Are these chains supposed to be built during install?

[placidchat]

installed zfs, and initiallised lxd. I don’t remember it being this chatty a couple of years ago.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.