From aeb2790839cee75e99d03254a261475d619a0c6f Mon Sep 17 00:00:00 2001 From: Alexandra Aldershaab Date: Tue, 18 Feb 2025 10:32:38 +0100 Subject: [PATCH] removed tool recs and adr --- .../ADRs/Cillium_as_network_plugin.md | 22 ------------------- docs/hardware_ready/_index.md | 12 +++++----- 2 files changed, 6 insertions(+), 28 deletions(-) delete mode 100644 docs/hardware_ready/ADRs/Cillium_as_network_plugin.md diff --git a/docs/hardware_ready/ADRs/Cillium_as_network_plugin.md b/docs/hardware_ready/ADRs/Cillium_as_network_plugin.md deleted file mode 100644 index ea26ea3..0000000 --- a/docs/hardware_ready/ADRs/Cillium_as_network_plugin.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -title: Use Cillium as Network Plugin ---- - -| status: | date: | decision-makers: | -| --- | --- | --- | -| proposed | 2025-02-12 | Alexandra Aldershaab | - - -## Context and Problem Statement - -A CNI plugin is required to implement the Kubernetes network model - -## Considered Options - -* Cillium -* Calico - -## Decision Outcome - -Chosen option: Cillium, because it was recommended at a knowledge sharing event by a company running large scale Kubernetes on prem. If we go with Talos, this is also the only CNI plugin they have a guide on how to use with Talos. - diff --git a/docs/hardware_ready/_index.md b/docs/hardware_ready/_index.md index f12feea..c86bab2 100644 --- a/docs/hardware_ready/_index.md +++ b/docs/hardware_ready/_index.md @@ -11,9 +11,9 @@ A virtualisation layer can benefit via abstracting the actual hardware, and enab In case virtualisation is chosen, the below recommendations are what you would run in your VM. For setting up your VM’s we recommend Talos with KubeVirt. ## Decision Matrix -| Problem domain | Description | Reason for importance | Tool recommendation | -|:---:|:---:|:---:|:---:| -| Kubernetes Node Operating System | The Operating System running on each of the hosts that will be part of your Kubernetes cluster | Choosing the right OS will be the foundation for building a production-grade Kubernetes cluster | Talos Linux | -| 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 (iscsi) OpenEBS (iscsi) | -| 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 | Containerd (embedded in Talos??? But maybe always containerd anyways?) | -| Network plugin (CNI) | Plugin used for cluster networking | A CNI plugin is required to implement the Kubernetes network model | [Cilium](Cillium_as_network_plugin.md) | +| Problem domain | Description | Reason for importance | Tool recommendation | +|:---:|:---:|:---:|:----------------------------------------:| +| Kubernetes Node Operating System | The Operating System running on each of the hosts that will be part of your Kubernetes cluster | Choosing the right OS will be the foundation for building a production-grade Kubernetes cluster | | +| 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 | | +| 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 | |