# Nodes

MetaKube manages the lifecycle of your cluster's Nodes.

> [!NOTE]
>
> **Info**
>
> There are no dedicated "control plane" nodes, since the control plane is managed by MetaKube in our infrastructure. Only the Kubernetes API is accessible.

## Terminology

The term "Node" is convoluted and often used for various types of things. To be precise, this is why we distinguish between different concepts.

### Node

A Node is the *Kubernetes resource* that represents Kubernetes' logical concept of a server hosting Pods.

- In MetaKube, Nodes are backed by OpenStack servers in an OpenStack network.
- A Node object is created when Kubelet first registers it with the Kubernetes API.

### MachineDeployment

A MachineDeployment is a logical abstraction of a *group* of Kubernetes Nodes in the cluster.

- It's used to control [rolling updates](<https://documentation.syseleven.de/en/prior-docs/metakube-core/concepts/nodes/machinedeployments/#rolling-update>).
- It's comparable to a Kubernetes [Deployment](<https://kubernetes.io/docs/concepts/workloads/controllers/deployment/>), for Nodes instead of Pods.

### MachineSet

MachineSets represent a set of Kubernetes Nodes with the *same configuration*.

- MachineSets are owned by a MachineDeployment
- They are gradually scaled up or down in [rolling updates](<https://documentation.syseleven.de/en/prior-docs/metakube-core/concepts/nodes/machinedeployments/#rolling-update>).
- They're comparable to [ReplicaSet](<https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/>).

### Machine

A Machine represents the "physical" server underlying a specific Kubernetes Node.

- Machines are immutable
- Machines (and their respective Nodes) are replaced during [rolling updates](<https://documentation.syseleven.de/en/prior-docs/metakube-core/concepts/nodes/machinedeployments/#rolling-update>).
