Very good instructor, highly recommend this video to anyone trying to get a high level overview of Kubernetes and Orchestration. Thanks so much @DevOps Journey!
This video was a beautiful and easy-to-follow introduction for me to Kubernetes. I can't believe I've been putting off learning for so long thinking it was something super complicated. Thank you, Brad.
Great video, using it as a refresher. Don't forget to manually delete your old configmaps when adding new ones by changing their version-number, the 'k delete -f v3.yml' will leave those behind.
Thank you so very much It's a beautiful presentation There much to learn And you made the learning very easy Much appreciate the immense time and effort you put into it
Hold on a second! Are you somehow related to the Action Labs guy?! Not only do you kinda look like each other, but you're both masters at explaining really complicated subjects and making it look easy! Awesome!
The diagram at 9:28 seems confusing. You've got one state machine diagram object (AWS ELB) and it pipes directly to a "Front End Service". What's the point of a load balancer if it doesn't distribute load and just throws it at a single thing (Front End Service)? Is the Front End Service replicated somehow to make it so the AWS ELB actually distributes load across the Front End Service in case one Front End Service is unable to handle requests? One other thing: if the load balancer is the absolute most critical part of the architecture (failure there means Kubernetes doesn't even matter anymore), why hasn't kubernetes been used to do replicasets on the load balancer? Is this just because kubernetes can't or is it so complicated to do so, it's not worth it? Seems like the tool doesn't do what it should do, which is provide high availability and you're making exceptions for the load balancer to do things its own way. Also, it sounds like you're putting a load balancer in front of a load balancer. This sounds way too weird.
Hi, Can you please make a video & explain how to write an ansible playbook in a very simple way? It's a bit confusing regarding spaces & hyphens. I think it's called indentation. In terraform as well its used spaces and curly brackets etc I am not from a programming or DevOps background so find it confusing where & when these things should be applied in both the tools. Also Variables. Kindly if possible please explain it in simple terms as if you are explaining it to someone who does not have any knowledge about it. Please it's a request. Kindly reply
I had no clue about kubernetes before this video, so pls don'tget me wrong I. At 50:25 you had too many pods (10) and you said we can leave our comments. I believe that happened because you did not terminate the previous terminal where you run the previous minikube service. So once you run apply command for v3, minikube started updating according to the v3 file(terminating the old ones and creating the new pods). I close my terminal before running kubectl apply -f v3.yaml command and I have only 5 pods and I dontsee any terminating pods, I guess they were terminated after I close the terminal. Thanks a lot for these videos. Greetings from Istanbul/Turkey.
when we install the Virtual Box on windows and setup few VMs in it. After installing Docker Desktop VMs fail to start on windows. is any one faced similar error.
Ok, I have been using another port like 8181 to expose the service as I had Jenkins running on localhost:8080 (I thought it'll clash but service opens up entirely different 3rd port on browser... I still need to understand what happens). But exposing the service at 8080 as said in video works. Maybe this hello-node container is configured to listen to 8080 by default.
![Kubernetes Crash Course for Absolute Beginners [NEW]](http://i.ytimg.com/vi/s_o8dwzRlu4/mqdefault.jpg)
![Kubernetes Crash Course for Absolute Beginners [NEW]](/img/tr.png)
Planning on doing more Kubernetes content for September/October. Let me know what kind of other Kubernetes content you would like to see!
Probably we want real time application deployment on kubernetes cluster.. Plz make a separate video on it!!
Devops
Please do a complete Kubernetes series..after which may be aks or eks
helm, operator, istio, knative, RBAC off the top of my head
Hey, great tutorial thanks. Was wondering if you are planning to do tutorial for AKS? Thanks 🙂
Very good instructor, highly recommend this video to anyone trying to get a high level overview of Kubernetes and Orchestration. Thanks so much @DevOps Journey!
Guys, You deserve 30m reviews and more. Keep doing it. Wonderful videos. Give it some more time and you"ll get millions of subscribers
Thanks so much! Comments like yours and sharing these videos will help us get there in no time ❤️
This video was a beautiful and easy-to-follow introduction for me to Kubernetes. I can't believe I've been putting off learning for so long thinking it was something super complicated.
Thank you, Brad.
Great video, using it as a refresher. Don't forget to manually delete your old configmaps when adding new ones by changing their version-number, the 'k delete -f v3.yml' will leave those behind.
One of the best DevOps content available on the internet #hero
lets fknnn goo, this is what I wanted!
Thank you so very much
It's a beautiful presentation
There much to learn
And you made the learning very easy
Much appreciate the immense time and effort you put into it
Hold on a second! Are you somehow related to the Action Labs guy?! Not only do you kinda look like each other, but you're both masters at explaining really complicated subjects and making it look easy! Awesome!
It will be great if you consider making a premium course. I love the way you break down concepts.
Would be great to see K8s on AWS! Thanks!
Thanks!
very well prepared and narrated, great job
I love your videos man! You make it look super easy!
Thank you so much for your video it gave me more understanding of Kubernetes
Great video. Thanks a lot for sharing this
Yes. This is what we want. Thanks a lot.
At 3:45 and 3:50 it seems the Scheduler and Controllers do the same thing?
very good explanation
"everything should work out ok" famous last words.
The diagram at 9:28 seems confusing. You've got one state machine diagram object (AWS ELB) and it pipes directly to a "Front End Service". What's the point of a load balancer if it doesn't distribute load and just throws it at a single thing (Front End Service)? Is the Front End Service replicated somehow to make it so the AWS ELB actually distributes load across the Front End Service in case one Front End Service is unable to handle requests? One other thing: if the load balancer is the absolute most critical part of the architecture (failure there means Kubernetes doesn't even matter anymore), why hasn't kubernetes been used to do replicasets on the load balancer? Is this just because kubernetes can't or is it so complicated to do so, it's not worth it? Seems like the tool doesn't do what it should do, which is provide high availability and you're making exceptions for the load balancer to do things its own way. Also, it sounds like you're putting a load balancer in front of a load balancer. This sounds way too weird.
Great content, simple and neat 👌👌👌
One simple question, what is the cli tool u r using ?
Legend thanks man!
just awesome
thanks for the video
Amazing
Thanks!!
Thank you for all your work, I have a question! How do you make PowerShell look like this?
It's windows terminal + zsh/starship. I go over my setup in this video ruclips.net/video/XBU_6OSlgyI/видео.htmlsi=wLAaXfWZDAQpP1Rn
Hi,
Can you please make a video & explain how to write an ansible playbook in a very simple way? It's a bit confusing regarding spaces & hyphens. I think it's called indentation. In terraform as well its used spaces and curly brackets etc
I am not from a programming or DevOps background so find it confusing where & when these things should be applied in both the tools. Also Variables. Kindly if possible please explain it in simple terms as if you are explaining it to someone who does not have any knowledge about it.
Please it's a request. Kindly reply
I had no clue about kubernetes before this video, so pls don'tget me wrong I. At 50:25 you had too many pods (10) and you said we can leave our comments. I believe that happened because you did not terminate the previous terminal where you run the previous minikube service. So once you run apply command for v3, minikube started updating according to the v3 file(terminating the old ones and creating the new pods). I close my terminal before running kubectl apply -f v3.yaml command and I have only 5 pods and I dontsee any terminating pods, I guess they were terminated after I close the terminal. Thanks a lot for these videos. Greetings from Istanbul/Turkey.
Here's how you can create an alias for kubectl in Powershell:
Set-Alias -Name k -Value kubectl
@Devops Journey I might be wrong here but doesn't m here means "thousandth of a core". This means it 50m should only be 5%.
yeah it would be 5%. Maybe I said something differently in the video? Do you have a timestamp?
@@DevOpsJourney Thank for confirming. It's 53:30.
Thanks for sharing, I enjoy K8s and Docker content these day.
when we install the Virtual Box on windows and setup few VMs in it. After installing Docker Desktop VMs fail to start on windows. is any one faced similar error.
When I first do 'minikube service hello-node -n prod' (my deployment is in prod namespace) I get a connection refused page. How to resolve this?
Ok, I have been using another port like 8181 to expose the service as I had Jenkins running on localhost:8080 (I thought it'll clash but service opens up entirely different 3rd port on browser... I still need to understand what happens). But exposing the service at 8080 as said in video works. Maybe this hello-node container is configured to listen to 8080 by default.
ᵖʳᵒᵐᵒˢᵐ
Oh wow insane content. Generated about 7 pages of notes. 🫡
Awesome content, thanks so much!