DevOps ToolBox

I've never really worked with Kubernetes before and this was certainly a useful introduction. I now feel pretty equipped to dive a little deeper and really get comfortable with the tools. I particularly appreciated the complementary visuals when covering the context and theory. I would recommend to anyone looking to get stuck in (assuming you know your way around the terminal).

Omer did an awesome job breaking down some pretty complex stuff into something I could actually understand. The diagrams he used were spot on for explaining new concepts. I really got a lot out of the content, and I feel like my understanding of Kubernetes has leveled up big time. The intro was great too. I loved how he gave all the context and background on why Kubernetes was created. I felt like I had a decent understanding but it definitely helped fill in gaps I knew I had and gaps I didn't know I had. Honestly, I'm so glad I could pause and replay the videos because I needed to do that a lot to really get the hang of things. It's not the instructor's fault at all; the material is just dense (or maybe that's just me, haha). But seriously, I'd totally recommend this course to anyone who wants to dive into Kubernetes, especially if you're up for taking your time to really absorb everything. Feedback (that I don't feel are worth dropping a star rating since this may just be a me thing): - I think summarizing what we reviewed at the end of the videos using the diagrams creating at the beginning may have helped. - I would like to feel like I have a better understanding on the creation of kubernetes yaml files. They were just there and available. What's Omer's process for creating those yaml files? Does he have templates saved somewhere that are copy/pasted and then change the name and metadata. - When starting the `minikube tunnel`, Omer mentioned "minikube tunnel figures we have a load balancer service named frontend". I was originally curious why? After testing, I found that minikube tunnel is aware of running services. Regardless of their name or how many, minikube tunnel watches for new services and automatically tunnels new services and stops tunnelling deleted services. It's not limited to just one service per tunnel. Only 1 tunnel instance can exist at a time and it can handle multiple services - My terminal wouldn't tab autocomplete kubernetes commands which led to me trying `k edit deployment redis` dropping `.apps` from `deployment.apps` which still worked. After looking it up, it's to tell kubernetes which api resource to refer to. There may be deployments under both the core API group AND under the apps API group. Both groups having an api resource with the same name of deployments but having differing functionalities. Kubernetes is smart though and can usually extrapolate the right api group to default to based on context and version.