Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Cillium for the CNI #12

Merged
merged 5 commits into from
Feb 19, 2025
Merged

Use Cillium for the CNI #12

Show file tree
Hide file tree
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
d4c8e04
added ADR and link in tool stack regarding cilium
housa Feb 18, 2025
a651bf4
made the adr slightly better i think
housa Feb 18, 2025
bc15f94
rebased and fixed conflicts
housa Feb 18, 2025
fe64d60
docs(ADR): provides richer context for cilium ADR
Gertmeister Feb 18, 2025
0db2295
refactor(ADR): adds @Gertmeister as decision-maker of Cilium ADR
Gertmeister Feb 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions docs/hardware_ready/ADRs/Cilium_as_network_plugin.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
---
title: Use Cillium as Network Plugin
---

| status: | date: | decision-makers: |
| --- | --- | --- |
| proposed | 2025-02-18 | Alexandra Aldershaab |


## Context and Problem Statement

A CNI plugin is required to implement the Kubernetes network model

## Considered Options

* Flannel
* Cilium
* Calico

## Decision Outcome

Chosen option: Cillium, because we believe it is the future of CNI's.

We looked at Flannel, since it is embedded in Talos, but we wanted a plugin that would support Network policies, which flannel do not.

Calico, while supporting Network policies, just doesn't offer the vast range of smart stuff cilium does.

### 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, …}
* … <!-- numbers of consequences can vary -->
2 changes: 1 addition & 1 deletion docs/hardware_ready/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,4 +16,4 @@ In case virtualisation is chosen, the below recommendations are what you would r
| 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 | |
| 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) |