prasannavl
commented
11 months ago Related issue: https://github.com/k3d-io/k3d/issues/838
Firewall related info:
ufw: inactive.
iptables:
$ sudo iptables --list
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
NETAVARK_FORWARD all -- anywhere anywhere /* netavark firewall plugin rules */
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain NETAVARK_FORWARD (1 references)
target prot opt source destination
ACCEPT all -- anywhere 10.89.1.0/24 ctstate RELATED,ESTABLISHED
ACCEPT all -- 10.89.1.0/24 anywhere nf-tables rulesets:
$ sudo nft list ruleset
# Warning: table ip nat is managed by iptables-nft, do not touch!
table ip nat {
chain POSTROUTING {
type nat hook postrouting priority srcnat; policy accept;
counter packets 9790 bytes 1325950 jump NETAVARK-HOSTPORT-MASQ
ip saddr 10.89.1.0/24 counter packets 275 bytes 21688 jump NETAVARK-2EE7F3DEE5FA2
}
chain NETAVARK-HOSTPORT-SETMARK {
counter packets 1 bytes 60 meta mark set mark or 0x2000
}
chain NETAVARK-HOSTPORT-MASQ {
meta mark & 0x00002000 == 0x00002000 counter packets 1 bytes 60 masquerade
}
chain NETAVARK-HOSTPORT-DNAT {
tcp dport 33977 counter packets 6 bytes 360 jump NETAVARK-DN-2EE7F3DEE5FA2
}
chain PREROUTING {
type nat hook prerouting priority dstnat; policy accept;
fib daddr type local counter packets 316 bytes 22502 jump NETAVARK-HOSTPORT-DNAT
}
chain OUTPUT {
type nat hook output priority -100; policy accept;
fib daddr type local counter packets 2467 bytes 181491 jump NETAVARK-HOSTPORT-DNAT
}
chain NETAVARK-2EE7F3DEE5FA2 {
ip daddr 10.89.1.0/24 counter packets 0 bytes 0 accept
ip daddr != 224.0.0.0/4 counter packets 247 bytes 16150 masquerade
}
chain NETAVARK-DN-2EE7F3DEE5FA2 {
ip saddr 10.89.1.0/24 ip daddr 0.0.0.0 tcp dport 33977 counter packets 0 bytes 0 jump NETAVARK-HOSTPORT-SETMARK
ip saddr 127.0.0.1 ip daddr 0.0.0.0 tcp dport 33977 counter packets 0 bytes 0 jump NETAVARK-HOSTPORT-SETMARK
ip daddr 0.0.0.0 tcp dport 33977 counter packets 0 bytes 0 dnat to 10.89.1.15:6443
}
}
# Warning: table ip filter is managed by iptables-nft, do not touch!
table ip filter {
chain NETAVARK_FORWARD {
ip daddr 10.89.1.0/24 ct state related,established counter packets 52106 bytes 153831198 accept
ip saddr 10.89.1.0/24 counter packets 40762 bytes 2399333 accept
}
chain FORWARD {
type filter hook forward priority filter; policy accept;
counter packets 411233 bytes 520621661 jump NETAVARK_FORWARD
}
}
table ip6 filter {
}
Env
Also tried: k3d from manual install without nix, just for the sake of it though it shouldn't make a difference. Same issue.
What did you do
sudo $(which k3d) cluster create local(sudo due to my docker socket access)What did you do afterwards?
Copy over config to user account, since it was k3d was run as root
cat /root/.kube/config > ~/.kube/configRun kubectl to connect to the cluster
kubectl cluster-infoor any other kubectl commandsScreenshots or terminal output
Which OS & Architecture
k3d runtime-infoWhich version of
k3dk3d versionWhich version of docker
docker versionanddocker info