This message was deleted.
# k3da
adamant-kite-43734
02/21/2023, 6:07 PMThis message was deleted.
v
victorious-mouse-54341
02/21/2023, 6:50 PMWhen I describe the server node, I have this annotation:
<http://k3s.io/internal-ip|k3s.io/internal-ip>: 192.169.7.7victorious-mouse-54341
02/21/2023, 7:16 PMIn k3s it looks like this is accomplished via:
server --node-ip 192.169.7.10victorious-mouse-54341
02/21/2023, 7:26 PMI tried the following and neither set the server node IP. Still 192.169.7.7.
I feel that I'm really close though....
k3d cluster create doctorconsul --network doctorconsul_wan --api-port 127.0.0.1:6443 --k3s-arg="--disable=traefik@server:0" -p "8502:443@loadbalancer --node-ip 192.169.7.10"k3d cluster create doctorconsul --network doctorconsul_wan --api-port 127.0.0.1:6443 --k3s-arg="--disable=traefik@server:0" -p "8502:443@loadbalancer --node-ip=192.169.7.10"victorious-mouse-54341
02/21/2023, 7:50 PMokay. looks like I was misunderstanding the k3s-args syntax. Changed it, but now am getting a node filter error. a little closer:
Copy code
$ k3d cluster create doctorconsul --network doctorconsul_wan --api-port 127.0.0.1:6443 -p "8502:443@loadbalancer" \
--k3s-arg="--disable=traefik@server:0" \
--k3s-arg="--node-ip=192.169.7.10"
INFO[0000] portmapping '8502:443' targets the loadbalancer: defaulting to [servers:*:proxy agents:*:proxy]
FATA[0000] K3sExtraArg '--node-ip=192.169.7.10' lacks a node filter, but there's more than one nodevictorious-mouse-54341
02/21/2023, 7:55 PMgot it.
victorious-mouse-54341
02/21/2023, 7:55 PMk3d cluster create doctorconsul --network doctorconsul_wan --api-port 127.0.0.1:6443 -p "8502:443@loadbalancer" --k3s-arg="--disable=traefik@server:0" --k3s-arg="--node-ip=192.169.7.10@servers:*"victorious-mouse-54341
02/21/2023, 7:56 PMWorks
145 Views