https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rke2
a
This message was deleted.
c
That's not 3 load balancers. That's the addresses of the three nodes that servicelb is running on.
c
Thanks @creamy-pencil-82913. Additionally, if my network plugin is Cilium, would there be any compatibility issues with using the load balancer from K3s(It appears that the load balancer in K3s is implemented using iptables.)?
I tried using 
<http://svccontroller.k3s.cattle.io/lbpool=pool1|svccontroller.k3s.cattle.io/lbpool=pool1>
and 
<http://svccontroller.k3s.cattle.io/enablelb=true|svccontroller.k3s.cattle.io/enablelb=true>
, but they didn't take effect in RKE2. The service still generates random IP addresses.
it seems that the correct label domain should be 
rke2
instead of 
k3s
. Therefore, the labels should be 
<http://svccontroller.rke2.cattle.io/lbpool=pool1|svccontroller.rke2.cattle.io/lbpool=pool1>
and 
<http://svccontroller.rke2.cattle.io/enablelb=true|svccontroller.rke2.cattle.io/enablelb=true>
.
c
yes. those are the k3s docs. for rke2, it is rke2 instead.
Open in Slack
PreviousNext
Powered by