diff --git a/arch-images/CNI_diagram.png b/arch-images/CNI_diagram.png
deleted file mode 100644
index 2c569b0229..0000000000
Binary files a/arch-images/CNI_diagram.png and /dev/null differ
diff --git a/architecture.md b/architecture.md
index cf8ffb61fe..7953460aeb 100644
--- a/architecture.md
+++ b/architecture.md
@@ -476,26 +476,6 @@ __Runtime network setup with CNM__
 5. Create bridge, TAP, and link all together with network interface previously
   created
 
-### CNI
-
-![CNI Diagram](arch-images/CNI_diagram.png)
-
-__Runtime network setup with CNI__
-
-1. Create the network namespace.
-
-2. Get CNI plugin information.
-
-3. Start the plugin (providing previously created network namespace) to add a network
-  described into `/etc/cni/net.d/ directory`. At that time, the CNI plugin will
-  create the `cni0` network interface and a veth pair between the host and the created
-  netns. It links `cni0` to the veth pair before to exit.
-
-4. Create network bridge, TAP, and link all together with network interface previously
-  created.
-
-5. Start VM inside the netns and start the container.
-
 ## Storage
 Container workloads are shared with the virtualized environment through [9pfs](https://www.kernel.org/doc/Documentation/filesystems/9p.txt).
 The devicemapper storage driver is a special case. The driver uses dedicated block