wooden-coat-97755
05/17/2022, 2:00 PMmillions-alarm-86298
05/17/2022, 3:30 PMwooden-coat-97755
05/17/2022, 3:31 PMmillions-alarm-86298
05/17/2022, 3:32 PMwooden-coat-97755
05/17/2022, 3:33 PMwide-garage-9465
05/17/2022, 8:24 PMtype: LoadBalancer
.
It serves as the entrypoint to the k3d cluster, which is stateless and can thus easily be reconfigured, contrary to the k3s node containers (e.g. restarting them touches the cluster state).
By default, all ports configured via the --port
flags will be exposed on the k3d-lb and forwarded to the target node containers.
Due to this setup, you can use k3d cluster edit
to modify the exposed ports, without having to restart the node containers.
There are more benefits to it, but that's the gist of it.wooden-coat-97755
05/18/2022, 7:14 AM--no-lb
, but questioned I might need it in futuremillions-alarm-86298
05/18/2022, 7:17 AMwooden-coat-97755
05/18/2022, 7:18 AMmillions-alarm-86298
05/18/2022, 7:20 AMwooden-coat-97755
05/18/2022, 7:22 AMmillions-alarm-86298
05/18/2022, 7:23 AMIIUC
??wooden-coat-97755
05/18/2022, 7:23 AMmillions-alarm-86298
05/18/2022, 7:24 AMare saying k3d is modeled after AWS’s EKS+ELB, on the grounds the patternafaik no, it was not modelled after AWS but rather this is a common pattern in cloud arch
wooden-coat-97755
05/18/2022, 7:24 AMmillions-alarm-86298
05/18/2022, 7:24 AM