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
That MTU needs to be a string, i.e. 9001 -> "9001". I will expedite a fix for this, but for existing releases, if you want to enable the bandwidth plugin, I think the best way is to not set the environment variable and manually modify /etc/cni/net.d/10-aws.conflist on each node to add the following entry (at the bottom):
Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
What happened:
On EKS 1.23 updated AWS VPC CNI addon to 1.12.2-eksbuild.1 as recommended in AWS docs
Attach logs
the log from the aws-node pod says:
What you expected to happen:
The aws-node pod to come up fine.
How to reproduce it (as minimally and precisely as possible):
Tried to update AWS VPC CNI addon to latest as per the AWS docs.
Anything else we need to know?:
Environment:
kubectl version
):from:
amazon-k8s-cni:v1.11.4-eksbuild.1
to:amazon-k8s-cni:v1.12.2-eksbuild.1
cat /etc/os-release
):uname -a
):UPDATE: this only happens when this is set in cfg:
The text was updated successfully, but these errors were encountered: