Configuration required for v1.7.5 of CNI
See original GitHub issueAs part of the upgrade to CNI 1.7.5, we set the values for the following to be hard coded:
- name: ENABLE_POD_ENI
value: 'false'
- name: AWS_VPC_K8S_CNI_CONFIGURE_RPFILTER
value: 'false'
- name: AWS_VPC_K8S_CNI_CUSTOM_NETWORK_CFG
value: 'false'
- name: AWS_VPC_K8S_CNI_EXTERNALSNAT
value: 'false'
We should investigate if these values need to be configurable
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
Updating the Amazon VPC CNI plugin for Kubernetes add-on
Learn how to update the Amazon EKS Amazon VPC CNI plugin for Kubernetes add-on ... Several of the configuration variables for the plugin...
Read more >Releases · aws/amazon-vpc-cni-k8s
Action Required For Upgrading. To upgrade to VPC CNI >=v1.12.0, you must upgrade to VPC CNI >=v1.7.x first. We recommend that you update...
Read more >https://raw.githubusercontent.com/aws/amazon-vpc-c...
... "fieldPath": "spec.nodeName" - "name": "WARM_ENI_TARGET" "value": "1" "image": "602401143452.dkr.ecr.us-west-2.amazonaws.com/amazon-k8s-cni:v1.7.5" ...
Read more >Updating the Amazon VPC CNI plugin for Kubernetes add-on
Learn how to manage the Amazon EKS Amazon VPC CNI plugin for Kubernetes add-on for your cluster.
Read more >aws-vpc-cni 1.1.15 · helm/aws
Parameter Description Default
affinity Map of node/pod affinities
cniConfig.enabled Enable overriding the default 10‑aws.conflist file false
cniConfig.fileContents The contents of the custom cni config file nil...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Hey @emiioan https://github.com/pulumi/pulumi-eks/pull/553
this will go out today 😃
We managed to allow through selinux the necessary permissions to allow cni pod to start on docker but it will still be good to add this feature and for sure it will be handy for others out there using docker as runtime. By default security context privilege is not defined in yaml provided by aws, but it will be great if you can add as argument to cluster and pulumi code to compute the yaml at runtime adding “privileged: true” to cni container. Any chances of a new PR and a release in v.0.23.0? 😃