And brace yourself for Helm, which is super-useful and murky when you first start tinkering with it.ĭue to the ever-evolving nature of Kubernetes, if you find an example stack somewhere which is a few years old, don't be surprised if it fails to deploy in your environment. And I know that just by naming these, I'm practically inviting others to point out alternatives. Otherwise, you're faced with having the kubectl docs handy at all times. For example, Lens or k9s can help with this.
#Docker and kubernetes the complete guide stephen grider crack
Minikube can make for a simple playground environment, if you want to remove the "first, set up Kubernetes" step and crack on with deployment examples.įwiw, having the tools to help you understand what's going on in a running cluster can be quite helpful, imo. Likewise if you want to learn about a cloud provider such as AWS if you don't know Linux or networking or network security or a number of other things, you're gonna have a rough time trying to learn about AWS. To the uninitiated, Linux has a lot of moving parts just trying to select your first distro to tinker with can result in many voices telling you "don't waste your time with that, get something used in enterprises" or "unless you've configured and compiled the kernel, you don't know anything" or many other comments which can be frustrating when you Just Want To Get Started.
Not a great analogy, but it would be a bit like saying "I want to learn Linux" when your best computer strengths lie in using MS Word and Excel. The thing is, Kubernetes has a lot of moving parts. I'm all about getting up to speed as quickly as possible. I don't mean any of this in a "you haven't earned your nerd creds until you've suffered greatly" sort of way. You may not need to go from start to finish with a flawless victory before you consider looking at the Kubernetes Cookbook, but I suspect that once you start digging into KTHW you'll discover other cool but relevant stuff simply trying to figure this out. More time with real world problems will improve upon that.Ĭhecking out the description of the Kubernetes Cookbook, it seems to me that you might fare better (from a learning perspective) to try your hand with Kubernetes The Hard Way. Being able to set up a simple Docker swarm and deploy example stacks using docker-compose while you poke around, check container states, get logs, etc will help to peel back the green curtain somewhat. Okay, reading the description of the Docker Cookbook I would hazard to guess that it will get you started, hopefully without sending you down stale paths. The earlier parts of the book were fairly good, fwiw. I got some book years ago that I used to start getting more familiar, and I found that it was heading in a direction which didn't help me as much as I'd hoped. I would say that you could learn about Docker basics without too many surprises. Warning: wall of text ahead! TL DR readjust your short-term goals These areas of technology are pretty established and yet continually evolving. I'm with u/UltraInstinct007 for the most part.
0 kommentar(er)
