🥳 aws-vpc-cni v1.18.1 Automated Release! 🥑

[eks-networking-bot]

aws-vpc-cni v1.18.1 Automated Chart Sync! 🤖🤖

Release Notes 📝:

v1.18.1

Release Notes

None

Changes since v1.18.0

• Bug - Mount /run/xtables.lock as FileOrCreate in Helm chart (@kwohlfahrt)
• Cleanup - remove unused Dockerfile (@sushrk)
• Dependency - Bump github.com/containernetworking/plugins from 1.4.0 to 1.4.1 (@dependabot)
• Dependency - Bump golang.org/x/sys from 0.17.0 to 0.18.0 in /test/agent (@dependabot)
• Dependency - Bump helm.sh/helm/v3 from 3.14.2 to 3.14.3 (@dependabot)
• Dependency - Bump github.com/prometheus/common from 0.48.0 to 0.52.2 (@dependabot)
• Dependency - Bump github.com/stretchr/testify from 1.8.4 to 1.9.0 (@dependabot)
• Dependency - Bump github.com/onsi/ginkgo/v2 from 2.14.0 to 2.17.1 (@dependabot)
• Enhancement - Update .go-version to 1.22.2 to fix CVE reports. (@orsenthil)

To manually apply this release:

kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.18.1/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.18.1/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.18.1/config/master/aws-k8s-cni-us-gov-west-1.yaml

cn:

kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/v1.18.1/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.18.1/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-3                                                 
amazon-k8s-cni-init:v1.18.1
amazon-k8s-cni:v1.18.1
amazon/aws-network-policy-agent:v1.1.1

[MrMarkW]

@jaydeokar @jayanthvn Could you help this PR get released?

[jaydeokar]

Thanks for bringing this to our attention. This should be fixed by #1104