Skip to content

Releases: aws/amazon-vpc-cni-k8s

v1.7.7 Release

11 Dec 18:48
Compare
Choose a tag to compare

This is a patch release to cleanly delete regular pods with PPSG enabled with force delete.

Changes since v1.7.6 -

Thanks to @SaranBalaji90 for the fix.

If you want to apply this config to one of your clusters:

kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.7.7/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.7
amazon-k8s-cni:v1.7.7

To use version v1.7.7 of the cni-metrics-helper in a cluster:

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

v1.7.6 Release

02 Dec 23:45
Compare
Choose a tag to compare

This is a patch release to support instances with EFA ENIs (https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/efa.html).

Changes since v1.7.5

Thanks to all the contributors!!!

If you want to apply this config to one of your clusters:

kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.7.6/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.6
amazon-k8s-cni:v1.7.6

To use version v1.7.6 of the cni-metrics-helper in a cluster:

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

v1.7.5 Release

08 Oct 03:33
Compare
Choose a tag to compare

This is a patch release to address issue #1246, #1250.

The issue is caused by init.sh script tries to grep host IP and could match more than one ENIs. The consequence is the CNI starting up will be failed.

Changes since v1.7.4

If you want to apply this config to one of your clusters:

kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.7.5/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.5
amazon-k8s-cni:v1.7.5

To use version v1.7.5 of the cni-metrics-helper in a cluster:

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

v1.7.4 Release

01 Oct 20:36
Compare
Choose a tag to compare

This is a patch release to address issue #1241 where the CNI will fail to start on kernels older than 4.6.

The issue is caused by the init container assuming that the net.ipv4.tcp_early_demux key will be present. The early TCP demux change that breaks TCP connections from kubelet to pods using per pod security groups was added in kernel 3.6, but the flag to disable it was not added until 4.6. This means using TCP health checks for per pod security groups requires at least Linux kernel 4.6.

Changes since v1.7.3

If you want to apply this config to one of your clusters:

kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.7.4/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.4
amazon-k8s-cni:v1.7.4

To use version v1.7.4 of the cni-metrics-helper in a cluster:

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

v1.7.3 Release

16 Sep 23:19
Compare
Choose a tag to compare

This is a patch release to address issue #1212 which affects clusters that use the AWS EKS Per Pod Security Group feature.

The only reason to use this version over v1.7.2 is to be able to turn off tcp_early_demux to unblock host TCP communication to pods on the same node using Per Pod SG, such as liveness/readiness checks. Using this version and setting DISABLE_TCP_EARLY_DEMUX to true in the initContainer config will slightly increase the latency for node local TCP connections.

This fix does NOT turn off tcp_early_demux by default since it is only needed when you need local TCP connectivity to pods using the security groups for pods on the same node.

Changes since v1.7.2

If you want to apply this config to one of your clusters:

kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.7.3/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.3
amazon-k8s-cni:v1.7.3

To use version v1.7.3 of the cni-metrics-helper in a cluster:

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

v1.7.2 Release

14 Sep 23:05
Compare
Choose a tag to compare

This is a patch release to address issues #737, #964, #989, #1070, #1094, #1100, #1101, and #1148. This also includes a version bump of Calico to v3.15.1 and some minor cleanups.

Changes since v1.7.1

If you want to apply this config to one of your clusters:

kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.7.2/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.2
amazon-k8s-cni:v1.7.2

To use version v1.7.2 of the cni-metrics-helper in a cluster:

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

v1.7.2 Release Candidate 1

04 Sep 01:02
Compare
Choose a tag to compare
Pre-release

This is a patch release to address issues #737, #964, #989, #1070, #1094, #1100, #1101, and #1148. This also includes a version bump of Calico to v3.15.1 and some minor cleanups.

Changes since v1.7.1

If you want to apply this config to one of your clusters:

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.2-rc1
amazon-k8s-cni:v1.7.2-rc1

To use version v1.7.2-rc1 of the cni-metrics-helper in a cluster:

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

v1.7.1 Release

26 Aug 17:31
Compare
Choose a tag to compare

This is a patch release to address issue #1159, Calico deletes routes with v1.7.0. This was fixed in PR #1166 .

Changes since v1.7.0

  • Bug - Calico deletes routes when using CNI v1.7.0 (#1166, @jayanthvn)
  • Improvement - enable manual override for VERSION in images (#1156, @nprab428)

If you want to apply this config to one of your clusters:

kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.7.1/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:v1.7.1

To use version v1.7.1 of the cni-metrics-helper in a cluster:

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

v1.7.0 Release

19 Aug 21:07
Compare
Choose a tag to compare

This is a feature rich release adding a lot of new improvements. The biggest changes are #972 - where we start storing IPAM state in a file and use this across restarts and #955 - to copy portmap and loopback binaries and set up rp_filter in an init-container. Because of these changes, upgrades should not be done by just editing the image tag.

Warning! If you use Calico, please use v1.7.1 instead because of issue #1159.

Thanks to all the contributors - @anguslees, @bnapolitan, @gyuho, @mogren, @nithu0115, @nprab428, @saiteja313, @willejs, @SaranBalaji90, @anguslees, @abhinavmpandey08, @bnapolitan!

Full changelog

  • Improvement - Use install command instead of cp (#1061, @mogren)
  • Improvement - Updated manifest configs with default env vars (#1057, @saiteja313)
  • Improvement - Default to random-fully (#1048, @mogren)
  • Improvement - Update probe settings (#1028, @mogren)
  • Improvement - Added warning if delete on termination is set to false for the primary ENI (#1024, @jayanthvn)
  • Improvement - Use sed as a stream editor and redirect to file (#1069, @willejs)
  • Improvement - JSON output format for the entrypoint script (#1066, @jayanthvn)
  • Improvement - Limit scope of logs writable by ipamd container (#987, @anguslees)
  • Improvement - Autogenerate per-region YAML manifests from a common template (#986, @anguslees)
  • Improvement - Persist IPAM state to local file and use across restarts (#972, @anguslees)
  • Improvement - Add init container (#955, @mogren)
  • Improvement - Refresh subnet/CIDR information periodically (#903, @nithu0115)
  • Improvement - Add ipamd changes for sg support (#1126, @mogren)
  • Improvement - Add support to setup pod network using VLANss (#1125, @SaranBalaji90)
  • Improvement - Improve CRI->checkpoint logic in the face of downgrades (#1123, @anguslees)
  • Improvement - Slash and burn unused code (#1115, @anguslees)
  • Improvement - Remove references to unused metadata owner-id (#1111, @anguslees)
  • Improvement - Remove old pre-1.3 migration code (#1110, @anguslees)
  • Improvement - Enable log config for the metrics agent (#1104, @mogren)
  • Improvement - Refactor ENI limit struct (#1035, @mogren)
  • Docs - Changed data type for variables in README (#1116, @abhinavmpandey08)
  • Docs - Fix docs links for cni-metrics-agent (#1072, @mogren)
  • Bug - Make metrics-helper docker logging statement multi-arch compatible (#1067, @nprab428)
  • Bug - Use limits from API for g4dn.16xlarge (#1086, @mogren)
  • Testing - scripts/lib: bump up tester to v1.4.0 (#1065, @gyuho)
  • Testing - Create script to run all release tests (#1106, @bnapolitan)
  • Testing - Add parallel testing to conformance (#1018, @bnapolitan)
  • Testing - Cache go packages in CircleCI (#1017, @bnapolitan)
  • Testing - Create roles by default for e2e test cluster creation (#994, @bnapolitan)
  • Testing - Cover bottlerocket cluster test (#1096, @bnapolitan)
  • Testing - Introduce automated performance testing (#1068, @bnapolitan)

To update your cluster to use this release in one of your clusters, you should download the sample aws-node daemonset config and edit it to match your region and settings, or alternatively for us-west-2 just:

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

To verify the update:

kubectl describe ds aws-node -n kube-system | grep Image | cut -d ":" -f 2-3

602401143452.dkr.ecr.us-west-2.amazonaws.com/amazon-k8s-cni:v1.7.0

To use version v1.7.0 of the cni-metrics-helper in a cluster:

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

v1.6.3 Release

16 Sep 19:06
Compare
Choose a tag to compare

The most important change in this release is a fix for #1008, the CNI pod crashloopbackoff due to incorrect instance metadata while fetching ENI issue, fixed in PR #1011.

Note! If you edit an existing v1.5.x CNI deployment, make sure to mount /var/run/dockershim.sock correctly!

Changes since v1.6.2

If you want to apply this config to one of your clusters:

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

If you instead edit your current deployment, make sure to mount /var/run/dockershim.sock correctly!

Verify the update:

kubectl describe daemonset aws-node -n kube-system | grep Image | cut -d "/" -f 2

amazon-k8s-cni:v1.6.3

To use version v1.6.3 of the cni-metrics-helper in a cluster:

kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/release-1.6.3/config/v1.6/cni-metrics-helper.yaml