microk8s is sets iptables policy FORWARD to DROP on reboot
See original GitHub issueI created a fresh install of ubuntu 18.04 minimal on a vmware esxi 6.7u1 host. i checked iptables -S
and got this output (truncated):
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
This is consistent, no matter how often i reboot. Then i installed microk8s and all looks fine:
robert@k:~$ sudo snap install microk8s --edge --classic
microk8s (edge) v1.13.1 from Canonical✓ installed
robert@k:~$ sudo iptables -S
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
<trimmed>
However, after a reboot:
robert@k:~$ sudo iptables -S
[sudo] password for robert:
-P INPUT ACCEPT
-P FORWARD DROP
-P OUTPUT ACCEPT
<trimmed>
I’ve attached the microk8s.inspect
tarball as
inspection-report-20181229_224350.tar.gz
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:11 (2 by maintainers)
Top Results From Across the Web
microk8s is sets iptables policy FORWARD to DROP on ...
I created a fresh install of ubuntu 18.04 minimal on a vmware esxi 6.7u1 host. i checked iptables -S and got this output...
Read more >About the iptables settings that kube-proxy sets at startup
The following settings are set in iptables when kube-proxy starts. Due to the DROP setting of ctstae invalid, communication will be dropped ......
Read more >Troubleshooting
If a pod is not behaving as expected, the first port of call should be the logs. First determine the resource identifier for...
Read more >Kubernetes NodePort and iptables rules
err…a non-kubernetes is using the NodePort!! A few weeks back at work, one of our kubernetes nodes was rebooted and as it was...
Read more >Docker changes IPtables FORWARD policy to DROP
I tried to set the policy in /etc/sysconfig/iptables but that doesn't help. This seems specific to Amazon Linux 2, I don't seem to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Adding
--iptables=false
to/var/snap/microk8s/current/args/dockerd
fixes it.This will no longer work cause new version of microk8s use
containerd
instead ofdockerd