Amazon VPC CNI vs Multus CNI
Amazon VPC CNI
github.comMultus CNI
github.comSide by side
| Figure | Amazon VPC CNI | Multus CNI |
|---|---|---|
| Price from | — | — |
| Free plan | — | — |
| Free trial | — | — |
| Open source | — | — |
| Windows | Yes | — |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 0 |
| Spec score · Container Networking Software | 7.6 (#12) | 7.0 (#21) |
| How it works | Its CNI plugin wires up the host and pod network stacks, while the ipamd daemon manages a warm pool of IP addresses and assigns addresses to pods. | Multus calls other CNI plugins to provide additional network interfaces to multi-homed pods. |
| Integrations | The repository documents use with Kubernetes, Amazon EKS managed add-ons, and a Helm chart. | The project gives VLAN, VXLAN and PTP as examples of networks reached through other CNI plugins. |
| Purpose | Amazon VPC CNI is a Kubernetes networking plugin that uses Elastic Network Interfaces on AWS to provide pod networking. | Multus CNI is a Kubernetes CNI meta-plugin that attaches multiple network interfaces to pods by calling other CNI plugins. |
| Support | The project directs users to the EKS networking best-practices and troubleshooting guides, GitHub issues, and the Kubernetes Slack #aws-vpc-cni channel. | The project directs users to open a GitHub issue or ask questions in the Network Plumbing Working Group Slack #general channel. |
In their own words
Amazon VPC CNI
Amazon VPC CNI has no write-up on Specifiction yet; its figures are above.