diff --git a/docs/hardware_ready/ADRs/Cilium_as_network_plugin.md b/docs/hardware_ready/ADRs/Cilium_as_network_plugin.md
index ea26ea3..ed4f4ad 100644
--- a/docs/hardware_ready/ADRs/Cilium_as_network_plugin.md
+++ b/docs/hardware_ready/ADRs/Cilium_as_network_plugin.md
@@ -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
@@ -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 -->
\ No newline at end of file