Deploying RKE2 with Metallb Issue - IP gets assigned to the loadbalancer but no ARP entries are showing up under the interfaces, ARP ping and curl fails to the deployed loadbalancer IP + port IP Pool and L2Advertisement config

apiVersion: <http://metallb.io/v1beta1|metallb.io/v1beta1>
kind: IPAddressPool
metadata:
  name: core-net-192.168.92.140-159
  namespace: metallb-system
spec:
  addresses:
  - 192.168.94.140-192.168.94.159
---
apiVersion: <http://metallb.io/v1beta1|metallb.io/v1beta1>
kind: L2Advertisement
metadata:
  name: metallb-pool
  namespace: metallb-system
spec:
  ipAddressPools:
  - core-net-192.168.99.140-159

How can we enable kubeproxy ipvs on the management cluster? (at the moment i only have one cluster with workernodes added to the management cluster)

kubeproxy:
      extra_args:
        ipvs-scheduler: lc
        proxy-mode: ipvs

do i need to deploy a separate cluster with workernodes for this? Thanks a lot for your input, if im on the wrong channel for these questions please let me know, i apologize in advance Posted in #rke2