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/
m (Welcome moved page AWS VPC CNI to AWS VPC CNI addon) |
(→Errors) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
* https://docs.aws.amazon.com/eks/latest/userguide/cni-iam-role.html | * https://docs.aws.amazon.com/eks/latest/userguide/cni-iam-role.html | ||
* https://github.com/aws/amazon-vpc-cni-k8s/releases | * https://github.com/aws/amazon-vpc-cni-k8s/releases | ||
| − | * Versions: v1.16.3, v1.16.2, v1.16.1, v1.16.0, v1.15.4, v1.7.0 | + | * Versions: v1.16.4, v1.16.3, v1.16.2, v1.16.1, v1.16.0, v1.15.4, v1.7.0 |
** Obtain version:<code>[[kubectl describe daemonset aws-node --namespace kube-system]] | grep amazon-k8s-cni: | cut -d : -f 3</code> | ** Obtain version:<code>[[kubectl describe daemonset aws-node --namespace kube-system]] | grep amazon-k8s-cni: | cut -d : -f 3</code> | ||
** <code>[[kubectl describe daemonset aws-node --namespace kube-system]] | grep amazon-k8s-cni: | cut -d : -f 3</code> | ** <code>[[kubectl describe daemonset aws-node --namespace kube-system]] | grep amazon-k8s-cni: | cut -d : -f 3</code> | ||
| Line 26: | Line 26: | ||
== News == | == News == | ||
* 08/2023 [[Amazon VPC CNI now supports Kubernetes Network Policies]] | * 08/2023 [[Amazon VPC CNI now supports Kubernetes Network Policies]] | ||
| + | |||
| + | == Errors == | ||
| + | * <code>[[InsufficientNumberOfReplicas]] [[The add-on is unhealthy because it doesn't have the desired number of replicas.]]</code> | ||
== Related == | == Related == | ||
Latest revision as of 12:33, 15 March 2024
Amazon VPC CNI plugin for Kubernetes is a Networking plugin for pod networking in Kubernetes using Elastic Network Interfaces on AWS
- 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.4, v1.16.3, 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 3kubectl describe pods -n kube-system aws-node | grep -w Image
- 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:
{"env": {"AWS_VPC_K8S_CNI_CUSTOM_NETWORK_CFG":"true","ENABLE_PREFIX_DELEGATION":"true","ENI_CONFIG_LABEL_DEF":"topology.kubernetes.io/zone","WARM_PREFIX_TARGET":"1"}}
Contents
News[edit]
Errors[edit]
InsufficientNumberOfReplicas The add-on is unhealthy because it doesn't have the desired number of replicas.
Related[edit]
- 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[edit]
- 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 - AWS EKS Addons: best practices,
vpc-cni, kube-proxy, coredns, aws-ebs-csi-driver, aws-efs-csi-driver, aws-guardduty-agent, amazon-cloudwatch-observability, aws eks describe-addon-versions, aws eks create-addon, aws eks list-addons
Advertising:
