Difference between revisions of "AWS VPC CNI addon"
Jump to navigation
Jump to search
↑ https://aws.github.io/aws-eks-best-practices/networking/vpc-cni/
| Line 8: | Line 8: | ||
| − | We strongly recommend that you update one minor version at a time. For example, if your current minor version is 1.9 and you want to update to 1.11, you should update to the latest patch version of 1.10 first, then update to the latest patch version of 1.11 | + | We strongly recommend that you update one minor version at a time. For example, if your current minor version is 1.9 and you want to update to 1.11, you should update to the latest patch version of 1.10 first, then update to the latest patch version of 1.11. <ref>https://aws.github.io/aws-eks-best-practices/networking/vpc-cni/</ref> |
Revision as of 16:33, 26 February 2024
Amazon VPC CNI plugin for Kubernetes
- https://docs.aws.amazon.com/eks/latest/userguide/managing-vpc-cni.html
- https://docs.aws.amazon.com/eks/latest/userguide/cni-iam-role.html
- https://github.com/aws/amazon-vpc-cni-k8s/releases
- Versions: v1.16.2, v1.16.1, v1.16.0, v1.15.4, v1.7.0
- Obtain version:
kubectl describe daemonset aws-node --namespace kube-system | grep amazon-k8s-cni: | cut -d : -f 3 kubectl describe daemonset aws-node --namespace kube-system | grep amazon-k8s-cni: | cut -d : -f 3
- Obtain version:
We strongly recommend that you update one minor version at a time. For example, if your current minor version is 1.9 and you want to update to 1.11, you should update to the latest patch version of 1.10 first, then update to the latest patch version of 1.11. [1]
Optional:
News
Related
- Working with the Amazon VPC CNI plugin for Kubernetes Amazon EKS add-on
- EKS best practices: https://aws.github.io/aws-eks-best-practices/networking/vpc-cni/
See also
- AWS VPC CNI,
aws-node (ipamd): (aws-node, aws-eks-nodeagent, aws-vpc-cni-init), cluster_addons: vpc-cni, aws-network-policy-agent:aws-eks-na-cli, AmazonEKS_CNI_Policy,AmazonEKS_CNI_Policy
Advertising:
