> Kubernetes has great documentation so new starters can get up to speed more quickly even if they don’t have experience with it. I strongly disagree. What fee

> Kubernetes has great documentation so new starters can get up to speed more quickly even if they don’t have experience with it. I strongly disagree. What feels easy for one developer may be super hard for others. For me, the Kubernetes tutorial [1] and documentation [2] [3] feels borderline incomprehensible. It introduces several abstract concepts at once without telling me what they really mean. It raises more questions than it answers. For example: > Kubernetes coordinates a highly available cluster of computers that are connected to work as a single unit. What does that even mean? Is that “single unit” the entire application? Or rather one component, e. g. the backend? You usually don’t have more than one service per container, right? So what exactly is the cluster here? Why is there not a single example? > The Control Plane is responsible for managing the cluster. The Control Plane coordinates all activities in your cluster, such as scheduling applications, maintaining applications' desired state, scaling applications, and rolling out new updates. We haven’t even established what the cluster is and how it relates to an application but now we’re already talking about several applications? I feel entirely lost. Ok, let’s look at another introductory page [2]. It says things like: > The worker node(s) host the Pods that are the components of the application workload. But it won’t tell me what a Pod is. So I click on the Pods link [3]. It says: > A Pod (as in a pod of whales or pea pod) is a group of one or more containers, with shared storage and network resources, and a specification for how to run the containers. A Pod's contents are always co-located and co-scheduled, and run in a shared context. A Pod models an application-specific "logical host": it contains one or more application containers which are relatively tightly coupled. In non-cloud contexts, applications executed on the same physical or virtual machine are analogous to cloud applications executed on the same logical host. I find that explanation outright hostile. Not a single example that a newbie can understand. Instead, a pile-up of more and more abstract concepts. I still have no clue how a Pod, a node, an application, its instances, its components and a cluster relates. I’m giving up here. This documentation is abysmal. How can the blog author possibly call this thing well-documented? [1]: https://kubernetes.io/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro/ https://kubernetes.io/docs/tutorials/kubernetes-basics/creat... [2]: https://kubernetes.io/docs/concepts/overview/components/ https://kubernetes.io/docs/concepts/overview/components/ [3]: https://kubernetes.io/docs/concepts/workloads/pods/ https://kubernetes.io/docs/concepts/workloads/pods/