Containers-roadmap: [EKS] [request]: Release CNI Plugin 1.4 for EKS

[mogren]

Tell us about your request
Next CNI release with all changes since CNI 1.3.2

https://github.com/aws/amazon-vpc-cni-k8s/milestone/5

Which service(s) is this request for?
EKS team, CNI plugin https://github.com/aws/amazon-vpc-cni-k8s

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Some major features have been added since the last release:

• Explicitly set the IP on secondary ENIs
• ENIConfig set by custom annotation or label names
• Fix return path of NodePort traffic when using Calico network policy.
• Many smaller bug fixes...

Are you currently working around this issue?
Some users are currently limited by not being able to use these new features.

Additional context
Tracking issue for CNI 1.4

[mogren]

Created a 1.4 Milestone

[StevenACoffman]

ref weaveworks/eksctl#736

[mogren]

Released on GitHub, but still not used in the default EKS AMI.

[StevenACoffman]

@tabern is this the AMI default now?

[mogren]

@StevenACoffman It's not yet the default.

We are working on a few minor tweaks, like updating metrics to work with the new prometheus endpoints (https://github.com/aws/amazon-vpc-cni-k8s/pull/413) and some Calico cleanups (https://github.com/aws/amazon-vpc-cni-k8s/pull/410, https://github.com/aws/amazon-vpc-cni-k8s/pull/421) before making it the default.

[StevenACoffman]

Where can we track the change to AMI default, if not this issue?

[StevenACoffman]

@mogren I see 1.4.1 just released with all the issues you mention merged. Is there a tracking issue for when 1.4.x will be the AMI default?

[tabern]

Hey @StevenACoffman this is actually the issue for tracking 1.4.2 as the AMI default. We closed it in error last week.

[mogren]

Still not the default, but we will roll it out soon.

[mogren]

Starting today, CNI v1.4.1 is the default for new EKS clusters. If you were using the old cni-metrics-helper, please update to the newer build.