So I’ve been learning Kubernetes for a couple of months now and I’ve only just discovered your channel. Your explanation is spot on and the best on CZcams I’ve seen. So this feels like an exam to check if my cluster is up to par. 😂. Keep up the good work and stay stubborn about longhorn volume names! I never knew you could manually create them after deployment.
Fantastic. I've been migrating my docker containers from my standalone docker server to a kubernetes cluster and your videos have been super helpful. Thank you!
Amazing series, I discovered your channel on Friday and watched the whole series. I have FINALLY managed to get a K8S cluster up after trying for months! I genuinely cannot rate you and your teaching style highly enough, thank you! P.S I'm not in IT at all! I'm actually a Plant Engineer by trade, I even failed GCSE IT.
Loving all your content. For the Longhorn volumes, I create the PV in the manifest. That way its created automatically and I can give it a reasonable name instead of an auto-generated one.
Hey Jim, great work on this video, thanks for taking the time to explain, to would I would say the dumb folk, to get us up to speed on this complicated kubernetes software that we all want to use. I am digesting the information and excited to be able to deploy applications now in the setup.
Thank you, @Jims-Garage! K8s cluster with k3s up and running . With Traefik and tls certificates (Ovh) . Third take, done. Amazing. I'm now wondering how to migrate a service wirh a backend database. Any hint? Thanks again.
Watching you struggling with the small fonts in WinScp and Nodepadd++ I wonder why you don't use Windows Terminal and VsCode on your Windows 11? Almost everybody does this in this YT space and looks better presenting it in a video.
Just correct me if am wrong, am wondering why Traefik and Pi-Hole are deployed on docker only and outside K8s cluster, was that for core reason, and what should be more secure?
Wonderful explanation! Regarding the deployment yaml, would it be necessary to specify how the replicas are divided across the worker nodes to establish high availability (i.e. if you have by chance 2 replicas on the same worker node and that worker node goes down) ? Saw this as an example in one of the Techno Tim videos: czcams.com/video/8DeG3qO-HIA/video.htmlsi=lFVt3QSb_KliO9I0&t=469
Thanks. That shouldn't be necessary, kubernetes would automatically heal and redeploy on the other node, there would be an intermittent loss of service though. You can experiment with spread topology, this is designed for this purpose: kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/
So I’ve been learning Kubernetes for a couple of months now and I’ve only just discovered your channel. Your explanation is spot on and the best on CZcams I’ve seen. So this feels like an exam to check if my cluster is up to par. 😂. Keep up the good work and stay stubborn about longhorn volume names! I never knew you could manually create them after deployment.
@@Dycell haha thanks. Be sure to check out my RKE2 Ansible video as well. Makes deployment a doddle
I'll like before watching. Will review later (just kidding, I know I love your videos!).
Haha, thanks 👍
Fantastic. I've been migrating my docker containers from my standalone docker server to a kubernetes cluster and your videos have been super helpful. Thank you!
Excellent, you're welcome 😁
Amazing series, I discovered your channel on Friday and watched the whole series. I have FINALLY managed to get a K8S cluster up after trying for months!
I genuinely cannot rate you and your teaching style highly enough, thank you!
P.S I'm not in IT at all! I'm actually a Plant Engineer by trade, I even failed GCSE IT.
That's awesome, well done. Thanks for the feedback
Amazing work Jim!
Thanks! :D
Thanks Jim!
You're welcome 😁
Loving all your content. For the Longhorn volumes, I create the PV in the manifest. That way its created automatically and I can give it a reasonable name instead of an auto-generated one.
Excellent video! Thank you so much for going through this and explaining it all.
Glad it was helpful!
Cant, wait to dive into this video. I have a few docker-compose i want to test out 😊.
Great, reach out on Discord if you get stuck
@@Jims-Garage yeah, sure 👍 il be in touch. I had a sneak peek at the video, can't wait to dive in.
Nice! well done:)
Thanks, appreciate the feedback
Hey Jim, great work on this video, thanks for taking the time to explain, to would I would say the dumb folk, to get us up to speed on this complicated kubernetes software that we all want to use. I am digesting the information and excited to be able to deploy applications now in the setup.
You're welcome, glad you found it useful.
Thank you, @Jims-Garage! K8s cluster with k3s up and running . With Traefik and tls certificates (Ovh) . Third take, done.
Amazing. I'm now wondering how to migrate a service wirh a backend database. Any hint? Thanks again.
Nice work! You'll need to follow the guide to recreate the database in Kubernetes, you'll also need to move the existing data over to a PVC
Can you tell us who to convert supabase docker to kubernetise to take it updated, cause kubernetise projet already existe but not updated ❤❤❤
Watching you struggling with the small fonts in WinScp and Nodepadd++ I wonder why you don't use Windows Terminal and VsCode on your Windows 11? Almost everybody does this in this YT space and looks better presenting it in a video.
Thanks for the feedback. I'll think about switching to it.
Just correct me if am wrong, am wondering why Traefik and Pi-Hole are deployed on docker only and outside K8s cluster, was that for core reason, and what should be more secure?
They're relics from past videos. I run both in Kubernetes. Security is fine on either if you configure it correctly.
thax@@Jims-Garage
Wonderful explanation! Regarding the deployment yaml, would it be necessary to specify how the replicas are divided across the worker nodes to establish high availability (i.e. if you have by chance 2 replicas on the same worker node and that worker node goes down) ? Saw this as an example in one of the Techno Tim videos: czcams.com/video/8DeG3qO-HIA/video.htmlsi=lFVt3QSb_KliO9I0&t=469
Thanks. That shouldn't be necessary, kubernetes would automatically heal and redeploy on the other node, there would be an intermittent loss of service though. You can experiment with spread topology, this is designed for this purpose: kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/