v1.13.0
VPC CNI version v1.13.0 adds support for the ENABLE_V6_EGRESS feature: https://github.com/aws/amazon-vpc-cni-k8s/tree/release-1.13#enable_v6_egress-v1130, which allows pods in an IPv4 cluster to connect to IPv6 endpoints.
Changes since v1.12.6
- Bug - Increase datastore pool at startup (@jdn5126 )
- Bug - Deallocate IP address according to warm IP target when multiple enis are present (@bikashmishra100 )
- Bug - Return success from CNI DEL when IPAMD is unreachable (@jdn5126 )
- Bug - Fix for aws-vpc-cni chart with tolerations to produce syntax valid yaml (@Bourne-ID )
- Bug - adding ip check for annotatePod in ipamd (@jerryhe1999 )
- Feature - Introduce DISABLE_LEAKED_ENI_CLEANUP to disable leaked ENI cleanup task (@jdn5126 )
- Feature - Add IPv6 egress support to eks IPv4 cluster (@wanyufe )
- Feature - feat(chart): Refactored image template logic for endpoint flexibility (@stevehipwell )
- Feature - add AWS_EC2_ENDPOINT variable for custom endpoint (@jihunseol )
- Improvement - Refactor egress-v4-cni plugin to support unit testing (@wanyufe )
- Improvement - Update instance limits and core plugins version in preparation for upcoming VPC CNI release (@jdn5126 )
- Improvement - refactoring eniconfig func to only take node as parameter (@haouc )
- Improvement - Remove go mod download from Dockerfiles (@jdn5126 )
- Improvement - Add apiVersion to MY_NODE_NAME (@jdn5126 )
- Improvement - install all core CNI plugins via init container (@jdn5126 )
- Improvement - Make all the aws vpc cni environmental variables case insensitive (@jerryhe1999 )
- Improvement - resource limit on init container in eks addon (@pdeva )
- Testing - Add integration test for POD v4/v6 egress traffic (@wanyufe )
To manually apply this release:
kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.13.0/config/master/aws-k8s-cni.yaml
Note that the following regions use different manifests:
us-gov-east-1:
kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.13.0/config/master/aws-k8s-cni-us-gov-east-1.yaml
us-gov-west-1:
kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.13.0/config/master/aws-k8s-cni-us-gov-west-1.yaml
cn:
kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.13.0/config/master/aws-k8s-cni-cn.yaml
To apply this release using helm:
Follow the installation instructions in https://github.com/aws/amazon-vpc-cni-k8s/blob/v1.13.0/charts/aws-vpc-cni/README.md#installing-the-chart
Verify the update:
$ kubectl describe daemonset aws-node -n kube-system | grep Image | cut -d "/" -f 2
amazon-k8s-cni-init:v1.13.0
amazon-k8s-cni:v1.13.0
To manually apply this release for CNI Metrics Helper:
kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.13.0/config/master/cni-metrics-helper.yaml
Note that the following regions use different manifests:
us-gov-east-1:
kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.13.0/config/master/cni-metrics-helper-us-gov-east-1.yaml
us-gov-west-1:
kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.13.0/config/master/cni-metrics-helper-us-gov-west-1.yaml
cn:
kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.13.0/config/master/cni-metrics-helper-cn.yaml
To apply this release using helm for CNI Metrics Helper:
Follow the installation instructions in https://github.com/aws/amazon-vpc-cni-k8s/blob/v1.13.0/charts/cni-metrics-helper/README.md#installing-the-chart
Verify the update for CNI Metrics Helper:
$ kubectl describe deployment cni-metrics-helper -n kube-system | grep Image | cut -d "/" -f 2
cni-metrics-helper:v1.13.0