This message was deleted.
# rke2
a
This message was deleted.
c
rke2 doesn’t use a configmap to configure kube-proxy, config is passed to kube-proxy on a per-node basis via
kube-proxy-arg
in the config file/
b
Oh, thanks. So I could just chuck the settings that would be otherwise defined in the cm, and restart the nodes?
c
if there are any args it wants you to add, you can add those to kube-proxy-arg on the node, and then restart the service
b
Ok. So edit the /etc/rancher/rke2/config.yaml, and append something like the following would do it? ''' - name: kube-proxy-args mode: "ipvs" ipvs: strictARP: true '''
c
no
Copy code
kube-proxy-arg:
 - "--proxy-mode=ipvs"
 - "--ipvs-strict-arp=true"
b
Ok, It's still not quite clicking, but I'm exhausted and probably just missing something obvious. I'm going to step away for a bit and maybe it will make more sense when I'm not running on empty. Thanks for the help.
s
Not sure why you would need IPVS on kube-proxy? I think I had MetalLB running quite easily on RKE2, nothing special. I switched to PureLB though as it offers easier route propagation (using OSPF or even RIP; I don't quite like BGP)...