Is there a hook in RKE2 + Canal to pass in `--flan...
# rke2
b
Is there a hook in RKE2 + Canal to pass in
--flannel-backend=none
for single node clusters? Flannel is causing issues because in some cases our nodes don't have a default gateway. There's some hacks we can put in place but I'd rater just disable it since we don't make use of the overlay at all.
c
pass that arg in to what?
I don’t believe you can run without ANY overlay network. How do you expect pods to do networking? You need to use one of the backends here: https://github.com/flannel-io/flannel/blob/master/Documentation/backends.md
In k3s, --flannel-backend=none turns off flannel entirely because you’re going to install a different CNI to provide pod networking. You can’t just disable it and replace it with nothing.
There is no option to the canal chart to run only calico for network policy, but disable flannel. You have no CNI without flannel. You would be left with only HostNetwork pods functional.
b
My understanding is that with Canal, flannel only enters the picture when there's node-node comms via vxlan (or whatever.). The Calico part seems to do all the heavy lifting on the node local side of things.
Maybe I should just use Calico instead.
c
No. Canal is Calico for network policy, and Flannel for pod network. If you remove flannel, you have no pod network.
b
From what I can see, calico-node (felix) is doing all the node-local stuff.
c
you still need something to set up the pod network, handle ipam, and so on.
b
ok that makes sense.
Then I need a way to set ConfigMap
kube-system/rke2-canal-config
:
canal_iface: <value>
oh can I just set it in
/etc/rancher/rke2/config.yaml
?
Copy code
cni: canal
canal-iface: eth1 # Or your desired network interface
that's what AI says.
c
correct
b
Thanks @creamy-pencil-82913