[Feature] Rancher RKE support #1092
Description
Is your feature request related to a problem? Please describe.
I would like to be able to deploy Liqo to a Rancher managed, k8s RKE cluster.
Describe the solution you'd like
I would like RKE to be a supported option when installing Liqo, similar to k3s https://doc.liqo.io/installation/?provider=K3s
Describe alternatives you've considered
The only install option that functions at all when attempting to install is k3s. When attempting kind or kubeadm, nothing happens.
Additional context
First two options do not do anything
$ export KUBECONFIG=~/k8s_configs/cluster1
$ liqoctl install kind -n cluster1
* Initializing installer... 🔌
* Retrieving cluster configuration from cluster provider... 📜
Error: kube-controller-manager not found
$ liqoctl install kubeadm -n cluster1
* Initializing installer... 🔌
* Retrieving cluster configuration from cluster provider... 📜
Error: kube-controller-manager not found
k3s does install, but the gateway fails to start
I0204 21:56:50.384961 1 tunnel-operator.go:519] added route for destination {169.254.100.1/32} on device {liqo.host}
E0204 21:56:50.468163 1 tunnel-operator.go:467] an error occurred while creating iptables handler: cannot create Liqo default chains: cannot retrieve chains in table -> nat : running [/sbin/iptables -t nat -S --wait]: exit status 3: modprobe: can't change directory to '/lib/modules': No such file or directory
iptables v1.8.7 (legacy): can't initialize iptables table `nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
E0204 21:56:50.468261 1 gateway-operator.go:142] an error occurred while creating the tunnel controller: cannot create Liqo default chains: cannot retrieve chains in table -> nat : running [/sbin/iptables -t nat -S --wait]: exit status 3: modprobe: can't change directory to '/lib/modules': No such file or directory
iptables v1.8.7 (legacy): can't initialize iptables table `nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
I0204 21:56:50.468287 1 gateway-operator.go:143] cleaning up gateway network namespace
I0204 21:56:50.515558 1 gateway-operator.go:147] cleaning up wireguard tunnel interface
When the above is happening on a cluster with Calico, calico gives the following errors. Providing in case they are insightful. The errors occur when applying https://doc.liqo.io/installation/advanced/#calico or not on a fresh cluster.
...
bird: KIF: Invalid interface address 240.1.0.129 for liqo.vxlan
...
I have tested with and without IPVS (which we use), I have tried flannel or calico (which we use).
I would also like to mention we use Rocky Linux, I am unsure if that plays a part in the issues I am encountering.
Thank you for developing Liqo, it looks very exciting and something we would very much love to use for building out our multi cluster infra more.