# Nodes

MetaKube manages the lifecycle of your cluster's Nodes.

> [!NOTE]
>
> **Info**
>
> MetaKube manages the control plane in our infrastructure, so no dedicated "control plane" nodes exist. The Kubernetes API provides the sole component accessible from outside the cluster. See [apiserver](<https://documentation.syseleven.de/en/products/metakube-core/concepts/networking/control-plane/apiserver/index.md>) for more details.

## Terminology

The term "Node" carries distinct meanings. To avoid confusion, we use distinct terms for each concept.

### Node

A Node is the *Kubernetes resource* that represents a server hosting Pods.

- In MetaKube, OpenStack servers in an OpenStack network back Nodes.
- Kubelet creates a Node object when it first registers the Node with the Kubernetes API.

### MachineDeployment

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

- It controls [rolling updates](<https://documentation.syseleven.de/en/products/metakube-core/concepts/nodes/machinedeployments/#rolling-update>).
- It resembles a Kubernetes [Deployment](<https://kubernetes.io/docs/concepts/workloads/controllers/deployment/>), but manages Nodes instead of Pods.

### MachineSet

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

- A MachineDeployment owns its MachineSets
- MetaKube scales them up or down during [rolling updates](<https://documentation.syseleven.de/en/products/metakube-core/concepts/nodes/machinedeployments/#rolling-update>).
- They resemble [ReplicaSet](<https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/>).

### Machine

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

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