From 177b53bb0337f5c9e06b34a7e84ba154b65e1b03 Mon Sep 17 00:00:00 2001 From: Alexandra Aldershaab Date: Tue, 8 Jul 2025 14:29:27 +0200 Subject: [PATCH 1/3] added adr for virtualisation with some initial text - wip --- docs/hardware_ready/ADRs/virtualisation.md | 39 ++++++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 docs/hardware_ready/ADRs/virtualisation.md diff --git a/docs/hardware_ready/ADRs/virtualisation.md b/docs/hardware_ready/ADRs/virtualisation.md new file mode 100644 index 0000000..4bd54f2 --- /dev/null +++ b/docs/hardware_ready/ADRs/virtualisation.md @@ -0,0 +1,39 @@ +--- +title: "Virtualisation" +date: "2025-07-08" +--- + + +| status: | date: | decision-makers: | +| --- | --- | --- | +| proposed | 2025-07-08 | Alexandra Aldershaab | + + +## Context and Problem Statement + +One important aspect is to determine whether the clusters should run on an OS directly on the machines, or if it makes sense to add a virtualisation layer. + +Running directly on the hardware gives you a 1-1 relationship between the machines and the nodes. This is not always advised if the machines are particularly beefy. Running directly on the hardware will of course have lower latency than when adding a virtualisation layer. + +A virtualisation layer can benefit via abstracting the actual hardware, and enable simple zero downtime hardware maintenance. + +For larger companies, it is usually possible to provision VM's from the IT department, and in that case the clear recommendation would alway be to just use what is available. + +Running several virtual machines on one physical machine’s resources, allows for more efficient use of physical servers + +## Considered Options + +* KubeVirt +* Incus +* Proxmox + +## Decision Outcome + +Chosen option: "{title of option 1}", because {justification. e.g., only option, which meets k.o. criterion decision driver | which resolves force {force} | … | comes out best (see below)}. + + +### Consequences + +* Good, because {positive consequence, e.g., improvement of one or more desired qualities, …} +* Bad, because {negative consequence, e.g., compromising one or more desired qualities, …} +* … From 1b2c04105471bf687a9a81748cf08cc14056617f Mon Sep 17 00:00:00 2001 From: Alexandra Aldershaab Date: Tue, 8 Jul 2025 14:31:35 +0200 Subject: [PATCH 2/3] add link to ADR --- docs/hardware_ready/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/hardware_ready/_index.md b/docs/hardware_ready/_index.md index 8f0ba49..f706310 100644 --- a/docs/hardware_ready/_index.md +++ b/docs/hardware_ready/_index.md @@ -9,4 +9,4 @@ title: Getting your hardware ready | Storage solution | The underlying storage capabilities which Kubernetes will leverage to provide persistence for stateful workloads | Choosing the right storage solution for your clusters needs is important as there is a lot of balance tradeoffs associated with it, e.g redundancy vs. complexity | [Longhorn](Longhorn_as_storage_solution.md) | | Container Runtime (CRI) | The software that is responsible for running containers | You need a working container runtime on each node in your cluster, so that the kubelet can launch pods and their containers | | | Network plugin (CNI) | Plugin used for cluster networking | A CNI plugin is required to implement the Kubernetes network model | [Cilium](Cilium_as_network_plugin.md) | -| Virtualisation | An optional layer between your hardware and your Kubernetes tech stack | In some scenarioes it might be benefitial to abstract the underlying hardeware away, and have everything running in virtual machines | | +| Virtualisation | An optional layer between your hardware and your Kubernetes tech stack | In some scenarioes it might be benefitial to abstract the underlying hardeware away, and have everything running in virtual machines | [virtualisation](virtualisation.md)) | From 7e80501f9c083f3f217708b8c9aad034cbc1b298 Mon Sep 17 00:00:00 2001 From: Alexandra Aldershaab Date: Tue, 8 Jul 2025 14:33:40 +0200 Subject: [PATCH 3/3] fix empty lines --- docs/hardware_ready/ADRs/virtualisation.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/hardware_ready/ADRs/virtualisation.md b/docs/hardware_ready/ADRs/virtualisation.md index 4bd54f2..27fce77 100644 --- a/docs/hardware_ready/ADRs/virtualisation.md +++ b/docs/hardware_ready/ADRs/virtualisation.md @@ -3,12 +3,10 @@ title: "Virtualisation" date: "2025-07-08" --- - | status: | date: | decision-makers: | | --- | --- | --- | | proposed | 2025-07-08 | Alexandra Aldershaab | - ## Context and Problem Statement One important aspect is to determine whether the clusters should run on an OS directly on the machines, or if it makes sense to add a virtualisation layer.