You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+26Lines changed: 26 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -757,6 +757,32 @@ Default: `false`
757
757
Setting `ENABLE_IMDS_ONLY_MODE` to `true` enables the CNI plugin to operate in environments with strict VPC or IAM restrictions where EC2 API access is limited or unavailable. In this mode, the CNI plugin relies solely on the Instance Metadata Service (IMDS) to retrieve information about ENIs (Elastic Network Interfaces) and determine IP addresses to assign. These ENIs are only discovered at startup, so ENIs and IPs must be pre-attached and pre-assigned before CNI plugin starts up.
758
758
Enabling this mode automatically sets `DISABLE_NETWORK_RESOURCE_PROVISIONING` and `DISABLE_LEAKED_ENI_CLEANUP` to `true`, as the CNI plugin will not make any EC2 API calls during operation.
759
759
760
+
761
+
#### `ENABLE_MULTI_NIC` (v1.20.0+)
762
+
763
+
Type: Boolean as a String
764
+
765
+
Default: `false`
766
+
767
+
The CNI plugin by default only manages network card 0 and assigns a single IP address to each Pod. Setting `ENABLE_MULTI_NIC` to `true` enables the Amazon VPC CNI plugin to manage all eligible network cards on supported multi-card instance types.
768
+
769
+
A network card will be managed if at least one of the following conditions is met:
770
+
771
+
a. The network card does not have any devices attached to it
772
+
b. The network card has an `efa` OR an `ena` device attached to it
773
+
c. The network card has an `efa-only` AND an `ena` device attached to it
774
+
775
+
## Annotations
776
+
777
+
#### Multi Homed Pods (v1.20.0+)
778
+
779
+
The `k8s.amazonaws.com/nicConfig: multi-nic-attachment` annotation enables multi-homing for a pod, allowing it to receive an IP address from each managed network card on the node. While this provides multiple network paths, applications must explicitly utilize these interfaces to take advantage of the additional bandwidth. To enable this feature, set `ENABLE_MULTI_NIC` to `true` in the Amazon VPC CNI configuration and schedule the pod on an instance type that supports multiple network cards. If you are using the AWS VPC CNI implementation of network policies, these policies are applied symmetrically to all interfaces of the pod.
780
+
781
+
Note -
782
+
Downgrade considerations
783
+
1. If the feature is enabled and you plan to downgrade the plugin from v1.20.0+, ensure that all multi-homed pods are removed first to prevent IP leaks and then set the `ENABLE_MULTI_NIC` to `false`.
784
+
2. Drain and remove the nodes to clean up any additional ENIs created by the Amazon VPC CNI plugin on network cards with index > 0
0 commit comments