Open warmbasket opened 3 months ago
This issue is currently awaiting triage.
SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted
label.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
It doesn't state there are multiple control planes. Just multiple nodes.
I could see a little background on etcd might be useful. Even if it's just a link to a reference stating what etcd is.
It states "A Kubernetes cluster that handles production traffic should have a minimum of three nodes because if one node goes down, both an [etcd] member and a control plane instance are lost, and redundancy is compromised." So wouldn't there be multiple control plane instances? Or is the single control plane lost? What's the control plane instance?
You then state "Minikube is a lightweight Kubernetes implementation that creates a VM on your local machine and deploys a simple cluster containing only one node."
The whole point of this page is to describe how Minikube is used to create a cluster only to find out that it can only create a single node 'cluster' if you can even call it that.
Minikube can be used to create local kubernetes environment using different available resources/drivers (docker, virtualbox) on your machine.
You can also create multinode cluster using minikube, but for simplicity it is write down for only 1 node. You can also check out minikube documentation for multinode cluster.
You can make a learning environment with more than one node, so we could fix the tutorial to not teach that the cluster is only one node.
The default is still one node.
The diagram in https://kubernetes.io/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro/ is unhelpful; we could make a better one.
https://k8s.io/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro/ does not clearly explain the objective: help you set up a Kubernetes cluster on your own (local?) environment, so that you can use that cluster for further learning.
Kubernetes contributors: specific sub-issues about improvements, eg like the ones I commented on, are welcome.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
You state " Each node has a Kubelet, which is an agent for managing the node and communicating with the Kubernetes control plane."
You then state "A Kubernetes cluster that handles production traffic should have a minimum of three nodes because if one node goes down, both an [etcd] member and a control plane instance are lost, and redundancy is compromised."
What is an etcd member? and how are there multiple instances of the control plane if there's only one control plane?
You then state "Minikube is a lightweight Kubernetes implementation that creates a VM on your local machine and deploys a simple cluster containing only one node."
The whole point of this page is to describe how Minikube is used to create a cluster only to find out that it can only create a single node 'cluster' if you can even call it that.