https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3d
a
This message was deleted.
c
Have you tried setting --node-ip and/or --node-external-ip on the node? Since klipper-lb uses the node addresses…
q
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
I’m not sure what the exact syntax for k3d is
q
(Future readers: 
--node-ip
and 
--node-external-ip
flags have no effect, apparently)
c
they do for servicelb, but perhaps not for the k3d loadbalancer
w
loadbalancer
is not a Kubernetes node, so k3s args have no effect on it. What do you want to achieve after all?
q
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.
149 Views
Open in Slack
PreviousNext
Powered by