Could you make more Rancher videos? it's a popular topic and there isn't much tutorials about making a self hosted Rancher setup with low end hardware specs ( load balancing )
Great video, thanks. It helped me in my project. i have already installed k3s on my two servers and up and running in less than the time I used to use installing k8s with kubeadm
@@CloudVersityOfficial Not harder than setting up a cluster for the first time, while learning how to do it, and all this for production environment:)) One of the super useful things you showed was the nip.io service - I didn't know about it. However, it doesn't seem to fit a production environment approach, so it would be awesome if you could explain like what are the most basic ways to expose services like a database to a local network in which the k3s cluster is located, and a service to the internet. In my case, I already exposed those using simple nodeport, but I know it's not ideal.
@@redmictian Thanks for the input. I'll put that on my todo list. :) Routing and securely exposing stuff always causes headaches and gets complicated pretty fast but I'll see what I can do. nip.io is for playground environments, as soon as you go in the direction of production environments your goal should be to have a valid DNS.
15:37 - Hi, how do you have the public IP's for EXTERNAL-IP? I get the private IPs instead. And also can you update this video with the newest versions? Thank you for your efforts and time
Is the process in the video only meant to work with linode VPS's, or should it work with google cloud VPS's as well? I I'm not sure why, but the process is not working for me with VPS's on google cloud. After installing ingress-nginx, "kubectl -n ingress-nginx get svc" is showing internal IP-addresses on the column "External IP" instead of the external ones. The VPS's have the port 80, 443, 6443 already open though. Did anybody have a similar problem? I checked the yaml file for installing ingress-nginx, and I couldn't find anything obvious.
Good question :) I ran into similar problems with AWS, Azure and GCP, that's why I like to use simple cloud providers like Linode for these kind of demos because they are easier to handle. The big cloud providers will give you a fake public ip address which seems to not be know by your actual VM. Just check it with "netstat -i" or similar. They just get NATed down the road until it hits your VM in their "private" network. This is just an assumption, I'm not 100% sure if this is a correct explanation so take it with caution. However there is a fix. You need to manually edit the ingress nginx svc "ingress-nginx-controller" and manually add spec.externalIPs: [] your public IP. A "kubectl -n ingress-nginx get svc" should now update and also list your public IP besides the private one. You can now proceed with the demo. I also updated the the ingress by adding the "spec.ingressClassName" which is necessary since v1.22. Cheerio.
@@CloudVersityOfficial Sorry a bit late, but.. I just tried what you suggested, and worked great! Thanks. This "problem" made me learn even more about kubernetes :) FYI, it looks like I needed to edit the services on both "ingress-nginx-controller" and "ingress-nginx-controller-admission", and add the external IPs on both. Cheers.
i'm trying to install k3s on a Raspberry Pi 4 Model B 4Gb, but i have some problem. First problem, when i install the master node, the installation give me a this error "Job for k3s.service failed because the control process exited with error code. See "systemctl status k3s.service" and "journalctl -xeu k3s.service" for details." Second problem, when i use " cat /var/lib/rancher/k3s/server/node-token" the console give me the error "permission denied". I don't know where is the problem :(
Thank you very much for your video. I'm doing a k3s cluster across 3 vm with tailscale and thanks to your tutorial I was able to create the server & node easly. I just got an error deploying the manifest ..... dial tcp cluster-ip:443 io/timeout ..... and if I find the solution I'll reply here.
Well I couldn't find a solution, I tried again reinstalling my vps and using your cmd but I end up always with the same error msg: Error from server (InternalError): error when creating "manifest.yaml": Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": Post "ingress-nginx-controller-admission.ingress-nginx.svc:443/networking/v1beta1/ingresses?timeout=10s": dial tcp 10.43.35.60:443: connect: connection refused
@@ugurserhattoy same issue: just delete the ingress-nginx-controller-admission in ingress-nginx namespace or just reinstall ingress-nginx by helm method. That's it.
Nope, just installing k3s and any sort of ingress controller won't give you ssl certificates out of the box. Feel free to check out a video I made exactly about this topic :) th-cam.com/video/deLW2h1RGz0/w-d-xo.html
I just recognized, that I linked to the wrong Twitter profile in this video :D 🔥 Social Media 🔥 Twitter ► twitter.com/cloud_versity Instagram ► instagram.com/cloudversity
I'm glad that it was helpful to you ;) Actually k3s will deploy workloads per default also on the server nodes. If you want to have you control plane separated from your workloads you can leverage from "taints". Here is a link to the k3s documentation which covers that point: rancher.com/docs/k3s/latest/en/installation/ha/#2-launch-server-nodes You can just add the option to the install command like: curl -sfL get.k3s.io | sh -s - server --node-taint CriticalAddonsOnly=true:NoExecute This should do the trick :)
Awesome video! You explained everything really well thank you! I’m looking forward to checking out more of your content
Still a great intro to K3s in 2024. Subbed for more. ❤
thanks for the demo and info, have a great day
if you get issues installing try to replace "--no-deploy traefik" with "--disable traefik"
it may be the fix for you
it did work for me
Could you make more Rancher videos? it's a popular topic and there isn't much tutorials about making a self hosted Rancher setup with low end hardware specs ( load balancing )
2/4/2023 it still works! Amazing! Thank you man you saved my life
Hi, how do you have the public IP's for EXTERNAL-IP?
I 'm in the middle of moving to another company where they use Rancher, so this video was really helpful
If only Rancher is mentioned I think it is `rke`, not k3s
Great video, thanks. It helped me in my project. i have already installed k3s on my two servers and up and running in less than the time I used to use installing k8s with kubeadm
Thank you! Very useful video!
Surprisingly, the video was super helpful, despite the views count!
This is some great feedback!
Feel free to subscribe if you interested in topic like this. Growing a new channel isn't that easy. ;)
@@CloudVersityOfficial Not harder than setting up a cluster for the first time, while learning how to do it, and all this for production environment:))
One of the super useful things you showed was the nip.io service - I didn't know about it. However, it doesn't seem to fit a production environment approach, so it would be awesome if you could explain like what are the most basic ways to expose services like a database to a local network in which the k3s cluster is located, and a service to the internet. In my case, I already exposed those using simple nodeport, but I know it's not ideal.
@@redmictian Thanks for the input. I'll put that on my todo list. :)
Routing and securely exposing stuff always causes headaches and gets complicated pretty fast but I'll see what I can do.
nip.io is for playground environments, as soon as you go in the direction of production environments your goal should be to have a valid DNS.
Thank you. This helped me setup the cluster on gcp gce vm. Cheers.
Great to hear that.
Good job!
Thank you =)
7:19 dockershim will be removed from kubernetes version 1.23 and as a result, docker will not work as a container runtime from then.
K3s is using containerd as a container runtime since a while. So no worries, everything in this video will still work :)
@@stephan_berlin Yes I'm aware. I was just making a comment at 7:19 because he said version 1.20.
@@justinkim7202 Ahh - gotcha!
15:37 - Hi, how do you have the public IP's for EXTERNAL-IP? I get the private IPs instead. And also can you update this video with the newest versions? Thank you for your efforts and time
Hi there, I added a note a while back in the README.md
Cheers :)
gitlab.com/cloud-versity/rancher-k3s-first-steps#important-note-for-aws-azure-gcp
Plz make more video for k3s. Thanks bro
Is the process in the video only meant to work with linode VPS's, or should it work with google cloud VPS's as well? I I'm not sure why, but the process is not working for me with VPS's on google cloud. After installing ingress-nginx, "kubectl -n ingress-nginx get svc" is showing internal IP-addresses on the column "External IP" instead of the external ones. The VPS's have the port 80, 443, 6443 already open though.
Did anybody have a similar problem? I checked the yaml file for installing ingress-nginx, and I couldn't find anything obvious.
Good question :) I ran into similar problems with AWS, Azure and GCP, that's why I like to use simple cloud providers like Linode for these kind of demos because they are easier to handle. The big cloud providers will give you a fake public ip address which seems to not be know by your actual VM. Just check it with "netstat -i" or similar. They just get NATed down the road until it hits your VM in their "private" network. This is just an assumption, I'm not 100% sure if this is a correct explanation so take it with caution. However there is a fix.
You need to manually edit the ingress nginx svc "ingress-nginx-controller" and manually add spec.externalIPs: [] your public IP. A "kubectl -n ingress-nginx get svc" should now update and also list your public IP besides the private one. You can now proceed with the demo.
I also updated the the ingress by adding the "spec.ingressClassName" which is necessary since v1.22.
Cheerio.
@@CloudVersityOfficial Thanks. I'll give it try later.
@@CloudVersityOfficial Sorry a bit late, but.. I just tried what you suggested, and worked great! Thanks. This "problem" made me learn even more about kubernetes :) FYI, it looks like I needed to edit the services on both "ingress-nginx-controller" and "ingress-nginx-controller-admission", and add the external IPs on both. Cheers.
@@3rdman99 Awesome!
Anyone found a better way of doing this without deleting any admission web hooks and editing service objects?
Do you maybe know how do you use external IP on gcp with k3s? I tried this example on GCP and it does not work.
i'm trying to install k3s on a Raspberry Pi 4 Model B 4Gb, but i have some problem. First problem, when i install the master node, the installation give me a this error "Job for k3s.service failed because the control process exited with error code.
See "systemctl status k3s.service" and "journalctl -xeu k3s.service" for details."
Second problem, when i use " cat /var/lib/rancher/k3s/server/node-token" the console give me the error "permission denied".
I don't know where is the problem :(
In the manifest.yaml, what IP is set for in the Host Ingress rules? Should this me my public IP , one of the the k3s public or private IP's?
The public IP from your ingress-nginx load balancer. Time stamp around 15:15
Might be good to update repo README with correct install option to "--disable" traefik". Seems the "no-deploy" flag is now deprated.
Thank you for the heads-up :) Updated the README immediately.
Thank you very much for your video.
I'm doing a k3s cluster across 3 vm with tailscale and thanks to your tutorial I was able to create the server & node easly.
I just got an error deploying the manifest ..... dial tcp cluster-ip:443 io/timeout ..... and if I find the solution I'll reply here.
Well I couldn't find a solution, I tried again reinstalling my vps and using your cmd but I end up always with the same error msg:
Error from server (InternalError): error when creating "manifest.yaml": Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": Post "ingress-nginx-controller-admission.ingress-nginx.svc:443/networking/v1beta1/ingresses?timeout=10s": dial tcp 10.43.35.60:443: connect: connection refused
I am facing the same issue. Does anybody have an idea?
@@janrenz7690 @ganon4u do you guys got a solution for that? I am facing it too.
@@ugurserhattoy same issue: just delete the ingress-nginx-controller-admission in ingress-nginx namespace or just reinstall ingress-nginx by helm method. That's it.
how to add more masters to the cluster?
Can k3s use for production environment? What will be the reasons if it's not recommended to use on production?
No reason not to use it in prod. It is meant for that. Just has a lighter foot print.
Does it automatically generate tls for a k3s server?
Nope, just installing k3s and any sort of ingress controller won't give you ssl certificates out of the box.
Feel free to check out a video I made exactly about this topic :)
th-cam.com/video/deLW2h1RGz0/w-d-xo.html
I just recognized, that I linked to the wrong Twitter profile in this video :D
🔥 Social Media 🔥
Twitter ► twitter.com/cloud_versity
Instagram ► instagram.com/cloudversity
hi, please make a how to create high availability kubernetes cluster video. for example 2 master 3 worker.
so this mean that master node also function a load balancer using nginx? correct me if im wrong. im still new to this. :)
As I set it up in this video, yes. But you can of course change this to your liking ;)
very helpful video, thank you. i have a question please, can we deploy the demo application in the agent node or only in the server node?
I'm glad that it was helpful to you ;)
Actually k3s will deploy workloads per default also on the server nodes. If you want to have you control plane separated from your workloads you can leverage from "taints". Here is a link to the k3s documentation which covers that point: rancher.com/docs/k3s/latest/en/installation/ha/#2-launch-server-nodes
You can just add the option to the install command like: curl -sfL get.k3s.io | sh -s - server --node-taint CriticalAddonsOnly=true:NoExecute
This should do the trick :)
@@CloudVersityOfficial Thank you for the answer, i get it know.
Where to run these commands can be very confusing