This message was deleted.
# k3sa
adamant-kite-43734
05/26/2023, 4:53 PMThis message was deleted.
c
creamy-pencil-82913
05/26/2023, 5:23 PMtraefik is not a load balancer. traefik is an ingress controller.
creamy-pencil-82913
05/26/2023, 5:24 PMload balancers handle services with type=LoadBalancer
creamy-pencil-82913
05/26/2023, 5:24 PMingress controllers handle routing traffic (usually http requests) as configured by Ingress resources.
creamy-pencil-82913
05/26/2023, 5:24 PMYou should check the Kubernetes docs on Service vs Ingress to understand the difference better.
creamy-pencil-82913
05/26/2023, 5:25 PMIn this case, you’re seeing Traefik exposed via a LoadBalancer service.
creamy-pencil-82913
05/26/2023, 5:25 PMServices are L3, Ingress are L7
m
mammoth-winter-72426
05/26/2023, 10:39 PMThankyou @creamy-pencil-82913 !! The ExecStart= should just be “k3s server” for the node that originally created the cluster while all nodes that join must have “k3s server —server —cluster-init +nodetoken” and same with agent except the cluster init obviously
c
creamy-pencil-82913
05/26/2023, 10:40 PMno
creamy-pencil-82913
05/26/2023, 10:40 PMthe first node should have
--cluster-initcreamy-pencil-82913
05/26/2023, 10:41 PMother servers that join should have
--server=<https://server>:xxxm
mammoth-winter-72426
05/26/2023, 10:47 PMOkay @creamy-pencil-82913 I’m going to make the ExecStart of the cluster creator node be ExecStart= K3s server —server —cluster-init
mammoth-winter-72426
05/26/2023, 10:50 PMI’m sorry I mean just:
K3s server —cluster-init
mammoth-winter-72426
05/26/2023, 10:58 PMThe agent nodes need the “K3s agent —server + token” @creamy-pencil-82913
c
creamy-pencil-82913
05/26/2023, 10:58 PMcorrect
m
mammoth-winter-72426
05/26/2023, 11:00 PM@creamy-pencil-82913 thankyou! That is all for today! Have a great weekend
2 Views