Skip to content

Commit

Permalink
made the adr slightly better i think
Browse files Browse the repository at this point in the history
  • Loading branch information
housa committed Feb 18, 2025
1 parent 5f6332e commit aa18485
Showing 1 changed file with 13 additions and 3 deletions.
16 changes: 13 additions & 3 deletions docs/hardware_ready/ADRs/Cilium_as_network_plugin.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ title: Use Cillium as Network Plugin

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


## Context and Problem Statement
Expand All @@ -13,10 +13,20 @@ A CNI plugin is required to implement the Kubernetes network model

## Considered Options

* Cillium
* Flannel
* Cilium
* 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.
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 -->

0 comments on commit aa18485

Please sign in to comment.