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: docs/book/src/topics/eks/pod-networking.md
+20Lines changed: 20 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,6 +97,26 @@ spec:
97
97
disableVPCCNI: true
98
98
```
99
99
100
+
If you are replacing Amazon VPC CNI with your own helm managed instance, you will need to set `AWSManagedControlPlane.spec.disableVPCCNI` to `true` and add `"prevent-deletion": "true"` label on the Daemonset. This label is needed so `aws-node` daemonset is not reaped during CNI reconciliation.
101
+
102
+
The following example shows how to label your aws-node Daemonset.
103
+
104
+
```yaml
105
+
apiVersion: apps/v1
106
+
kind: DaemonSet
107
+
metadata:
108
+
annotations:
109
+
...
110
+
generation: 1
111
+
labels:
112
+
app.kubernetes.io/instance: aws-vpc-cni
113
+
app.kubernetes.io/managed-by: Helm
114
+
app.kubernetes.io/name: aws-node
115
+
app.kubernetes.io/version: v1.15.1
116
+
helm.sh/chart: aws-vpc-cni-1.15.1
117
+
prevent-deletion: true
118
+
```
119
+
100
120
> You cannot set **disableVPCCNI** to true if you are using the VPC CNI addon.
101
121
102
122
Some alternative CNIs provide for the replacement of kube-proxy, such as in [Calico](https://projectcalico.docs.tigera.io/maintenance/ebpf/enabling-ebpf#configure-kube-proxy) and [Cilium](https://docs.cilium.io/en/stable/gettingstarted/kubeproxy-free/). When enabling the kube-proxy alternative, the kube-proxy installed by EKS must be deleted. This can be done via the **disable** property of **kubeProxy** in **AWSManagedControlPlane**:
0 commit comments