https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3s
a
This message was deleted.
b
curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC='server --cluster-init --disable=traefik --disable-kube-proxy --flannel-backend=none --disable-network-policy --no-deploy servicelb --tls-san=192.168.100.101 --tls-san k3s01.<mydomain>.xyz --cluster-domain <mydomain>.xyz' K3S_KUBECONFIG_MODE="644" K3S_TOKEN=<mytoken> sh -s -
Would this command be correct?
c
why are you disabling so many things?
are you deploying your own CNI, kube-proxy replacement, service, and ingress controller?
Is your cluster domain an existing domain, and does it conflict with your existing DNS zone?
b
It is all totally new to me. My plan was to use Cilium for kubeproxy. This is just for my home. Goal is to get Traefik and Authentik to work and see where it goes! 🙂 Its all new to me!
I have used Docker for years but really trying hard to get a k3s HA cluster working.
c
if you’re just starting out I would probably get a working cluster up with the defaults, and then once you know how to do that, start replacing components
Trying to learn how it works at the same time you’re trying to replace like 75% of the stuff it comes with is going to lead to a lot of frustration
b
Okey. i misunderstood then. i thought i had to replace kubeproxy for Cilium to work and MetalLB instead of ServiceLB.
@creamy-pencil-82913 Where should i start? a standard install without Traefik and install it with yml/helm? (I have a extra VM for kubectl and Helm and Cilium-CLI)
c
I mean yeah, if you want to use cilium’s kube-proxy replacement you need to disable kube-proxy, and you’d want to disable servicelb if you’re going to use metallb.
I’m not sure why you’re disabling the bundled traefik just to deploy your own though.
like I said, I would probably build a cluster using the default components first, and get that working. then rebuild it a couple more times, replacing one thing at a time
you don’t know how anything works now, so when something breaks you have no idea what is causing it
b
Very true! I just think i'm way to eager to get a cluster up! It have been a IT dream of mine for years but i just finally got a small little server start with.. the plan is to have the three nodes on the same machine to start with anyway!
i thought the bundled Traefik was a way older version and i seen lots recommending to install Traefik after.. But honestly i don't remember why right now.
c
its not that old
b
Good! 🙂 As i said it's all new and thought it would be nice to just start with Traefik 3 because i have seen 2.x
Reminded myself now. why i needed Helm, Cert-Manager, MetalLB.. i just wanted to use my Porkbun TLS with Traefik..
c
I’m not familiar with that. Will it work with Traefik’s Cert-Manager support?
b
yes
i just installed certmanager
it is horrible to be all alone with all of this.. but right now i'm trying to update cert-manager config for self-signed to start with.. but like everything else i get stuck on every single step.
"kubectl apply -f " oh.. that was easy..
no.. that did not work..
yeeey! got that part done! so now i should have self-signed cert installed for cert-manager..
@creamy-pencil-82913 Oh! now i understood what you said. So i don't need Cert-Manager because Porkbun is on the Traefik provider list!
6 Views
Open in Slack
PreviousNext
Powered by