https://rancher.com/ logo
#k3d
Title
# k3d
a

adamant-kite-43734

11/11/2022, 7:37 PM
This message was deleted.
c

creamy-pencil-82913

11/11/2022, 7:49 PM
Have you tried setting --node-ip and/or --node-external-ip on the node? Since klipper-lb uses the node addresses…
q

quick-midnight-5000

11/11/2022, 8:00 PM
Just to make sure I'm getting the nodefilter right, that would be:
--k3s-arg="--node-external-ip 192.168.64.200@loadbalancer:0"
right?
c

creamy-pencil-82913

11/11/2022, 8:39 PM
I’m not sure what the exact syntax for k3d is
q

quick-midnight-5000

11/11/2022, 10:39 PM
(Future readers:
--node-ip
and
--node-external-ip
flags have no effect, apparently)
c

creamy-pencil-82913

11/11/2022, 11:22 PM
they do for servicelb, but perhaps not for the k3d loadbalancer
w

wide-garage-9465

11/15/2022, 6:40 AM
loadbalancer
is not a Kubernetes node, so k3s args have no effect on it. What do you want to achieve after all?
q

quick-midnight-5000

11/15/2022, 6:14 PM
The goal is to have the loadbalancer take requests from a specified IP like
192.168.64.200
rather than
127.0.0.1
I can do this with MetalLB by specifying an IP pool, but I have yet to achieve that with k3d.
148 Views