This message was deleted.
# k3da
adamant-kite-43734
03/14/2025, 2:54 PMThis message was deleted.
w
wide-garage-9465
03/14/2025, 2:58 PMWell, the nodes themselves (docker containers) are gone now.
Now you have to tell Kubernetes, that they're gone for good via
kubectl delete nodeb
blue-train-85231
03/14/2025, 2:59 PMahh
blue-train-85231
03/14/2025, 2:59 PMatleast those pods are now terminating.. I would have figured k8s would detect the pods wasn't responding and re-spin them on the remaining node
blue-train-85231
03/14/2025, 3:00 PM(the only ready one)
blue-train-85231
03/14/2025, 3:00 PMvery weird it didn't detect pods wasn't actually running ?
blue-train-85231
03/14/2025, 3:07 PMcan I spin down the last agent? or did k3d taint the server as to not run some pods (like cni).. or how does that work in k3d ?
w
wide-garage-9465
03/14/2025, 3:08 PMSingle server is fine.
That's a K3s thing btw.
k3d tries not to do anything non-essential with respect to Kubernetes.
b
blue-train-85231
03/14/2025, 3:08 PMso k3s server alone will work fine and run everything ?
w
wide-garage-9465
03/14/2025, 3:09 PMI mean, you can just check if there's a taint using kubectl
wide-garage-9465
03/14/2025, 3:10 PMkubectl describe nodeTaints: <none>b
blue-train-85231
03/14/2025, 3:12 PMperfect. zero taints
blue-train-85231
03/14/2025, 3:12 PMI'll remove the last agent then
blue-train-85231
03/14/2025, 3:12 PMthank you
blue-train-85231
03/14/2025, 3:12 PMwhy is there a seperate k3d-management-cluster-serverlb node too?
blue-train-85231
03/14/2025, 3:14 PMnow I have just 1 node in nodes list 🙂
w
wide-garage-9465
03/14/2025, 3:15 PMThe serverlb is a k3d auxiliary required for port-mappings to the cluster. It enables you to modify port-mappings after the cluster is created.
👍 1
7 Views