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
+21-1Lines changed: 21 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,8 +7,26 @@ When creating a EKS cluster the Amazon VPC CNI will be used by default for Pod N
7
7
## Using the VPC CNI Addon
8
8
You can use an explicit version of the Amazon VPC CNI by using the **vpc-cni** EKS addon. See the [addons](./addons.md) documentation for further details of how to use addons.
9
9
10
+
## Using Custom VPC CNI Configuration
11
+
If your use case demands [custom networking](https://docs.aws.amazon.com/eks/latest/userguide/cni-custom-network.html) VPC CNI configuration you might already be familiar with the [helm chart](https://github.com/aws/amazon-vpc-cni-k8s) which helps with the process. This gives you access to ENI Configs and you can set Environment Variables on the `aws-node` DaemonSet where the VPC CNI runs. CAPA is able to tune the same DaemonSet through Kubernetes.
10
12
11
-
## Increase node pod limit
13
+
The following example shows how to turn on custom network config and set a [label definition](https://github.com/aws/amazon-vpc-cni-k8s#eni_config_label_def).
14
+
15
+
```yaml
16
+
kind: AWSManagedControlPlane
17
+
apiVersion: controlplane.cluster.x-k8s.io/v1beta1
18
+
metadata:
19
+
name: "capi-managed-test-control-plane"
20
+
spec:
21
+
vpcCni:
22
+
env:
23
+
- name: AWS_VPC_K8S_CNI_CUSTOM_NETWORK_CFG
24
+
value: "true"
25
+
- name: ENABLE_PREFIX_DELEGATION
26
+
value: "true"
27
+
```
28
+
29
+
### Increase node pod limit
12
30
You can increase the pod limit per-node as [per the upstream AWS documentation](https://aws.amazon.com/blogs/containers/amazon-vpc-cni-increases-pods-per-node-limits/). You'll need to enable the `vpc-cni` plugin addon on your EKS cluster as well as enable prefix assignment mode through the `ENABLE_PREFIX_DELEGATION` environment variable.
0 commit comments