5 ms·
I started with k8s beginning this year and from my point of view, the documentation is not good - and a major pain point when trying to get started. Each part
by cygned 8y ago
I started with k8s beginning this year and from my point of view, the documentation is not good - and a major pain point when trying to get started.
Each part on its own is good and well written, but it lacks the overall picture and does not connect pieces well enough. For example, the schema definitions for the all the configuration files are not linked from the official docs (at least I wasn’t able to find them). The description of how to get started with an On Premise setup is scattered over multiple pages from multiple tools.
So from my point of view, things could be improved for beginners.
- tomsthumb 8y agoThe kubernetes up and running book gives a better big picture view than the documentation online does. It does a thorough job of developing motivation and context for using a broad swath of the system in a cohesive way.
- cygned 8y agoI actually own that book and I definitely recommend it!
- geerlingguy 8y agoThis! So many parts of the docs are excellent in isolation, but if you jump from one page on Ingress Controllers to a page on Pod replicas, to a page on something else, the pages are obviously written by different authors who use different services (e.g. Google Cloud vs, bare metal vs. Azure) and some of the docs assume you’re also using said service, but don’t explicitly call it out. And then you wonder why some command or example isn’t working the same in minikube or some test bed environment. Too much of my ‘getting up and running’ time was spent figuring out things on my own based on Stack Exchange, blog posts, and experimentation.