Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
m
mammoth-winter-72426
05/26/2023, 4:53 PMGood morning everyone!
I’m confused because I created 2 different Load balancer services in a namespace, 1 load balancer is for UDP and the other is for another protocol.
But when I check to see what pods are running in the “Kube-System” namespace I can see the following:
“svclb-service1UDP”
“svclb-service2DifferentProtocol”
“svclb-traefik”
Now after a little research, I found K3s automatically comes with traefik load balancer along with the default Kubernetes load balancer.
But why does K3s by default come with both?
I think the answer is because traefik is an ingress component while K3s LB is just a default svclb…..
I found using the traefik ingress just has more features and is specifically better for security purposes compared to the default K3s load balancer service. But are both using the cloud? I don’t think the K3s LB is….
c
creamy-pencil-82913
05/26/2023, 5:23 PMtraefik is not a load balancer. traefik is an ingress controller.
load balancers handle services with type=LoadBalancer
ingress controllers handle routing traffic (usually http requests) as configured by Ingress resources.
You should check the Kubernetes docs on Service vs Ingress to understand the difference better.
In this case, you’re seeing Traefik exposed via a LoadBalancer service.
Services 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
the first node should have
--cluster-initother 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
I’m sorry I mean just:
K3s server —cluster-init
The 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