Manuel Buil

This will be fixed by https://github.com/k3s-io/k3s/pull/4114

This should be enabled by: https://github.com/k3s-io/k3s/blob/master/pkg/agent/syssetup/setup.go#L43-L53 Not by the CNI. The container runtime is the one creating the network namespace

> @manuelbuil that's interesting, any idea why it wouldn't have worked? It's been a while but I definitely needed to change a setting in the Calico config to fix it....

Thanks for the proposal, I believe it make a lot of sense. I think that the first approach should be trying to integrate Nebula using the extension backend. That backend...

One important aspect we should consider is how we specify the nebula interface to kubelet. By the time flannel executes all the nebula commands and thus sets up the nebula...

> I've been reading the documentation you sent and it's been very helpful! I've been thinking how this could be possible to implement and this is what I'm thinking so...

For v0.18.0 this is fixed, could you check?

> Using `v0.19.1-1-gab7a3945` to get the right images (instead of v0.19.0) > > Hoping that the new CNI plugin won't mix too poorly with the old CNI plugins... > >...

> I am not sure if you want to keep this open until it is fixed so other people can find it or if you want to close it because...

> @manuelbuil any ideas? I suspect that perhaps some of the rules have changed between versions? It seems so but I don't think we have changed anything in that area....