Configuring EKS networking using the VPC CNI
As discussed previously, the AWS VPC CNI is installed by default, but you may need to upgrade the CNI to use prefix assignment mode, for example, or change a configuration parameter. The following sections will take you through configuration steps for common tasks.
Managing the CNI plugin
The simplest way to carry out an upgrade of the CNI for a new cluster is to apply the new Kubernetes manifest. The following code snippet will install version v1.9.1 onto your cluster and change the version as desired. Be aware, however, that downgrading the CNI version can be very tricky and, in some cases, will not work!
In a script or CI/CD pipeline, it’s often a good idea to be able to export the version of the currently running CNI (as long as it is deployed). The following code snippet will allow you to do that:
$ export CNI_VER=$(kubectl describe daemonset aws-node --namespace kube-system | grep Image | cut -d "/" -f...
