<p>This is the definition of a node in kubernetes docs:</p>
<p>&quot;A Node is a worker machine in Kubernetes and may be either a virtual or a physical machine, depending on the cluster.&quot;</p>
<p>My question is , what is the real use case scenario for creating new nodes ? Let's say I install kubernetes on my personal laptop, is it good practice to create multiple nodes on a single machine ? Let's say I have 8 cpus on my single machine , is it good practice to create a node for every cpu and allocate that resource to each node ?</p>
<p>Or is it a more common scenario that a node is a virtual machine in a server ?</p>

moth
<blockquote>
<p>Or is it a more common scenario that a node is a virtual machine in a server ?</p>
</blockquote>
<p>A k8s cluster always has multiple nodes, mostly in odd numbers. The reason behind having odd number of nodes is the Raft Algorithm implemented inside K8s data store (ETCD). It needs to maintain a quorum of at least <code>(n + 1)/2</code> nodes for Leader election. The minimum number for a stable quorum is 3. However, there are some flavors of K8s like K3s, MicroShift and MicroK8s that are designed to run on single nodes (for edge deployments). Check out this <a href="https://stackoverflow.com/questions/48845946/why-should-a-production-kubernetes-cluster-have-a-minimum-of-three-nodes">post</a> for further details.</p>
<blockquote>
<p>what is the real use case scenario for creating new nodes ? Let's say I install kubernetes on my personal laptop, is it good practice to create multiple nodes on a single machine</p>
</blockquote>
<p>You will only setup k8s on you local machine for learning purposes only. In this case, you k8s cluster will consist of only 1 node.</p>
<p>For production workloads, you will always use multiple servers to setup k8s clusters.</p>
