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
+7-5
Original file line number
Diff line number
Diff line change
@@ -226,7 +226,7 @@ Type: Integer as a String
226
226
227
227
Default: 9001
228
228
229
-
Used to configure the MTU size for attached ENIs. The valid range is from `576` to `9001`.
229
+
Used to configure the MTU size for attached ENIs. The valid range for IPv4 is from `576` to `9001`, while the valid range for IPv6 is from `1280` to `9001`.
230
230
231
231
#### `AWS_VPC_K8S_CNI_EXTERNALSNAT`
232
232
@@ -267,14 +267,14 @@ Default: empty
267
267
Specify a comma-separated list of IPv4 CIDRs to exclude from SNAT. For every item in the list an `iptables` rule and off\-VPC
268
268
IP rule will be applied. If an item is not a valid ipv4 range it will be skipped. This should be used when `AWS_VPC_K8S_CNI_EXTERNALSNAT=false`.
269
269
270
-
#### `POD_MTU` (v1.x.x+)
270
+
#### `POD_MTU` (v1.16.4+)
271
271
272
272
Type: Integer as a String
273
273
274
-
*Note*: The default value is set to AWS_VPC_ENI_MTU, which defaults to 9001 if unset.
274
+
*Note*: If unset, the default value is derived from `AWS_VPC_ENI_MTU`, which defaults to `9001`.
275
275
Default: 9001
276
276
277
-
Used to configure the MTU size for pod virtual interfaces. The valid range is from `576` to `9001`.
277
+
Used to configure the MTU size for pod virtual interfaces. The valid range for IPv4 is from `576` to `9001`, while the valid range for IPv6 is from `1280` to `9001`.
278
278
279
279
#### `WARM_ENI_TARGET`
280
280
@@ -598,7 +598,7 @@ Setting `ANNOTATE_POD_IP` to `true` will allow IPAMD to add an annotation `vpc.a
598
598
599
599
There is a known [issue](https://github.com/kubernetes/kubernetes/issues/39113) with kubelet taking time to update `Pod.Status.PodIP` leading to calico being blocked on programming the policy. Setting `ANNOTATE_POD_IP` to `true` will enable AWS VPC CNI plugin to add Pod IP as an annotation to the pod spec to address this race condition.
600
600
601
-
To annotate the pod with pod IP, you will have to add "patch" permission for pods resource in aws-node clusterrole. You can use the below command -
601
+
To annotate the pod with pod IP, you will have to add `patch` permission for pods resource in aws-node clusterrole. You can use the below command -
NOTE: Adding `patch` permissions to the `aws-node` Daemonset increases the security scope for the plugin, so add this permission only after performing a proper security assessment of the tradeoffs.
0 commit comments