Skip to content

Releases: aws/amazon-vpc-cni-k8s

Release 1.10.1

11 Nov 01:13
104354c
Compare
Choose a tag to compare

v1.10.1

Release Notes:

v1.10.1 removes IMDSv1 dependency from VPC CNI.

To apply this release:

kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.10.1/config/master/aws-k8s-cni.yaml

Verify the update:

$ kubectl describe daemonset aws-node -n kube-system | grep Image | cut -d "/" -f 2                                                   
amazon-k8s-cni-init:v1.10.1
amazon-k8s-cni:v1.10.1

Note:

Amazon EKS does not yet support IPv6. You can follow progress on this feature by subscribing to the issue for EKS IPv6 support on the containers roadmap.

Release 1.10.0

09 Nov 20:33
7b8e0e4
Compare
Choose a tag to compare

v1.10.0

Important

v1.10.0 version has a dependency on IMDSv1 access being available for Host Networking Pods. For clusters with IMDSv1 access disabled, please use v1.10.1 instead.

Release Notes:

v1.10.0 release introduces IPv6 support in VPC CNI. IPv4 mode is enabled by default. Please refer to ENABLE_IPv6 section for detailed information around IPv6 support in VPC CNI. Dual stack mode isn't supported. Refer to the troubleshooting doc for known issues/limitations.

Changes since v1.9.3:

Thanks to all the contributors ❤️ !!!

To apply this release:

kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.10.0/config/master/aws-k8s-cni.yaml

Verify the update:

$ kubectl describe daemonset aws-node -n kube-system | grep Image | cut -d "/" -f 2                                                   
amazon-k8s-cni-init:v1.10.0
amazon-k8s-cni:v1.10.0

Note:

Amazon EKS does not yet support IPv6. You can follow progress on this feature by subscribing to the issue for EKS IPv6 support on the containers roadmap.

Release 1.9.3

15 Oct 01:30
b0c4a07
Compare
Choose a tag to compare

v1.9.3

Changes since v1.9.1:

Thanks to all the contributors ❤️ !!!

To apply this release:

kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/release-1.9/config/v1.9/aws-k8s-cni.yaml

Verify the update:

$ kubectl describe daemonset aws-node -n kube-system | grep Image | cut -d "/" -f 2                                                   
amazon-k8s-cni-init:v1.9.3
amazon-k8s-cni:v1.9.3

v1.9.1 Release

14 Sep 17:31
8737163
Compare
Choose a tag to compare

v1.9.1

Changes since v1.9.0:

Thanks to all the contributors ❤️ !!!

To apply this release:

kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.9.1/config/v1.9/aws-k8s-cni.yaml

Verify the update:

$ kubectl describe daemonset aws-node -n kube-system | grep Image | cut -d "/" -f 2                                                   
amazon-k8s-cni-init:v1.9.1
amazon-k8s-cni:v1.9.1

v1.9.0 Release

26 Jul 18:14
be5d0b6
Compare
Choose a tag to compare

v1.9.0

The CNI v1.9.0 release will support higher pod density per node and also reduces the number of EC2 calls to create and attach more ENIs by leveraging the recent EC2 feature - Assigning prefixes to Amazon EC2 network interfaces. This feature is only supported on "nitro" based instances. Each secondary IP will be replaced by a (/28) prefix and IPAMD will derive a (/32) IP from these prefixes for pod IP allocation. Number of prefixes which can be attached to the ENI is still limited by the IP addresses per network interface per instance type- for instance a t3.medium can have 5 (/28)prefixes per ENI. Since the number of pods per node will increase, make sure the max pods are adjusted appropriately and keep in mind CPU and memory constraints will limit the number of pods that be deployed on a node. To help with the max pods computation we have added this helper script.

To enable the feature, set ENABLE_PREFIX_DELEGATION to true. This environment variable can be set to true or false while pods are running but kubelet maxPods has to be manually changed.

PS: This feature is available in all public regions and AWS GovCloud (US), with support in China (Beijing), and China (Ningxia) coming soon.

kubectl set env daemonset aws-node -n kube-system ENABLE_PREFIX_DELEGATION=true

With this feature we support WARM_PREFIX_TARGET and IPAMD will keep a free prefix in warm pool. We also support WARM_IP_TARGET and MINIMUM_IP_TARGET and IPAMD will allocate a new prefix if the existing prefixes are not sufficient to maintain the warm pool. This document talks about how these 3 warm targets impact the number of IPs available in the warm pool.

Since the IPs with this feature will be allocated from the prefixes, we won't be able to support downgrades. Also WARM_ENI_TARGET won't be supported with ENABLE_PREFIX_DELEGATION set to true.

Changes since v1.8.0:

To apply this release:

kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.9.0/config/v1.9/aws-k8s-cni.yaml

Verify the update:

$ kubectl describe daemonset aws-node -n kube-system | grep Image | cut -d "/" -f 2                                                   
amazon-k8s-cni-init:v1.9.0
amazon-k8s-cni:v1.9.0

v1.8.0 Release

10 Jun 03:03
de835a6
Compare
Choose a tag to compare

v1.8.0

Changes since v1.7.10:

Thanks to all the contributors ❤️ !!!

To apply this release:

kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.8.0/config/v1.8/aws-k8s-cni.yaml

Verify the update:

$ kubectl describe daemonset aws-node -n kube-system | grep Image | cut -d "/" -f 2                                                   
amazon-k8s-cni-init:v1.8.0
amazon-k8s-cni:v1.8.0

v1.7.10 Release

19 Mar 22:43
dba11f4
Compare
Choose a tag to compare

v1.7.10

Changes since v1.7.9:

  • Improvement - Multi card support - Prevent route override for primary ENI across multi-cards ENAs (#1396 by jayanthvn)

Currently P4 family supports more than one network card and IPAMD will ignore ENIs on non-zero network cards. IPAMD will continue to manage ENI allocation on network card 0 but will not manage ENIs on non-zero network cards.

To apply this release:

kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.7.10/config/v1.7/aws-k8s-cni.yaml

Verify the update:

$ kubectl describe daemonset aws-node -n kube-system | grep Image | cut -d "/" -f 2                                                   
amazon-k8s-cni-init:v1.7.10
amazon-k8s-cni:v1.7.10

1.7.10 Release Candidate 1

18 Mar 06:19
beed4a5
Compare
Choose a tag to compare
Pre-release

v1.7.10-rc1

Changes since v1.7.9:

  • Improvement - Multi card support - Prevent route override for primary ENI across multi-cards ENAs (#1396 by jayanthvn)

Currently P4 family supports more than one network card and IPAMD will ignore ENIs on non-zero network cards. IPAMD will continue to manage ENI allocation on network card 0 but will not manage ENIs on non-zero network cards.

To apply this release:

kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.7.10-rc1/config/v1.7/aws-k8s-cni.yaml

Verify the update:

$ kubectl describe daemonset aws-node -n kube-system | grep Image | cut -d "/" -f 2                                                   
amazon-k8s-cni-init:v1.7.10-rc1
amazon-k8s-cni:v1.7.10-rc1

v1.7.9 Release

18 Feb 22:52
710ca53
Compare
Choose a tag to compare

v1.7.9

Changes since v1.7.8:

  • Improvement - Adds http timeout to aws sessions (#1370 by couralex6)
  • Improvement - Switch calico to be deployed with the Tigera operator (#1297 by tmjd)
  • Improvement - Update calico to v3.17.1 (#1328 by lwr20)
  • Improvement - update plugins to v0.9.0 (#1362 by fr0stbyte)
  • Improvement - update github.com/containernetworking/plugins to v0.9.0 (#1350 by fr0stbyte)
  • Bug - Fix regex match for getting primary interface (#1311 by Jayanthvn)
  • Bug - Output to stderr when no log file path is passed (#1275 by couralex6)
  • Bug - Fix deletion of hostVeth rule for pods using security group (#1376 by SaranBalaji90)

To apply this release:

kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.7.9/config/v1.7/aws-k8s-cni.yaml

Verify the update:

$ kubectl describe daemonset aws-node -n kube-system | grep Image | cut -d "/" -f 2                                                   
amazon-k8s-cni-init:v1.7.9
amazon-k8s-cni:v1.7.9

v1.7.9 Release Candidate 1

08 Feb 22:43
b9b1a29
Compare
Choose a tag to compare
Pre-release

v1.7.9 Release Candidate 1

Changes since v1.7.8:

  • Improvement - Adds http timeout to aws sessions (#1370 by couralex6)
  • Improvement - Switch calico to be deployed with the Tigera operator (#1297 by tmjd)
  • Improvement - Update calico to v3.17.1 (#1328 by lwr20)
  • Improvement - update plugins to v0.9.0 (#1362 by fr0stbyte)
  • Improvement - update github.com/containernetworking/plugins to v0.9.0 (#1350 by fr0stbyte)
  • Bug - Fix regex match for getting primary interface (#1311 by Jayanthvn)
  • Bug - Output to stderr when no log file path is passed (#1275 by couralex6)
  • Bug - Fix deletion of hostVeth rule for pods using security group (#1376 by SaranBalaji90)

To apply this release:

kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/release-1.7/config/v1.7/release-candidate/aws-k8s-cni.yaml

Verify the update:

$ kubectl describe daemonset aws-node -n kube-system | grep Image | cut -d "/" -f 2                                                   
amazon-k8s-cni-init:v1.7.9-rc1
amazon-k8s-cni:v1.7.9-rc1