Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bridget doesn't play nicely with CentOS' firewall #8

Open
elFarto opened this issue Jan 15, 2021 · 1 comment
Open

Bridget doesn't play nicely with CentOS' firewall #8

elFarto opened this issue Jan 15, 2021 · 1 comment

Comments

@elFarto
Copy link

elFarto commented Jan 15, 2021

Bridget doesn't play nicely with CentOS (and probably RHEL) firewall by default as it sets the policy on the FORWARD chain to DROP. This I believe can be fixed by including the 'firewall' CNI plugin in the CNI script.

I think you need to add something like:

"plugins": [
      {
        "type": "firewall"
      }
    ]
@elFarto
Copy link
Author

elFarto commented Jan 20, 2021

I've done some more research into this, and it seems this is the correct configuration to use (I also had to rename the CNI file to a .conflist):

{
        "name": "bridget",
        "cniVersion": "0.4.0",
        "plugins": [{
                "type": "bridge",
                "bridge": "cbr0",
                "ipMasq": true,
                "mtu": 1500,
                "ipam": {
                        "type": "host-local",
                        "subnet": "10.244.0.0/16",
                        "rangeStart": "10.244.0.2",
                        "rangeEnd": "10.244.0.254",
                        "gateway": "10.244.0.1",
                        "routes": [
                                { "dst": "0.0.0.0/0" }
                        ]
                }
        },{
                "type": "firewall"
        }]
}

However, this is incompatible with the version of Kubernetes I have installed (v1.15), so I'm unable to test it completely. This is due to Kubernetes v1.15 only supporting CNI up to v0.3.1, and the firewall plugin requires v0.4.0 for some reason.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant