Difference between revisions of "K8s Container Network Interface (CNI)"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 8: | Line 8: | ||
* [[Calico]] | * [[Calico]] | ||
* [[Flannel]] | * [[Flannel]] | ||
| + | * [[Multus CNI]] | ||
| Line 25: | Line 26: | ||
* <code>[[kubelet]]</code>: <code>--network-plugin=cni</code> | * <code>[[kubelet]]</code>: <code>--network-plugin=cni</code> | ||
* [[Container Storage Interface (CSI)]] | * [[Container Storage Interface (CSI)]] | ||
| + | * [[Weave Net]] | ||
== See also == | == See also == | ||
Latest revision as of 10:05, 23 April 2024
Container Network Interface (CNI)
The Container Network Interface (CNI) plugin is selected by passing kubelet the --network-plugin=cni
- v1.18 Update CNI version to v0.8.5
- CKA v1.23 CKA v1.26: Choose an appropriate container network interface plugin
- CKA v1.18: Understand CNI
helm search repo eks | grep cni eks/aws-vpc-cni 1.1.10 v1.9.3 A Helm chart for the AWS VPC CNI
Related terms[edit]
- Kubernetes networking
- Podman v2.0.0 (Jun 2020), default Podman CNI configuration now sets
HairpinModeto allow communication between containers by connecting to a forwarded port on the host. kubeadmkubectl -n kube-system -l=k8s-app=kube-dns get podskubelet:--network-plugin=cni- Container Storage Interface (CSI)
- Weave Net
See also[edit]
- Kubernetes networking: Container Network Interface (CNI), VPC CNI, Multus CNI, Calico, Flannel
- Kubernetes networking: network policies, Network Policy Providers, CNI, Calico, flannel, Service mesh, Istio,
kube-proxy, coredns, AWS VPC CNI: vpc-cni, Kubernetes: Ingress controllers, IPVS, ServiceTypes:LoadBalancer, ClusterIP, NodePort, ExternalName, Endpoints, EndpointSlices, Kubernetes DNS,svc.cluster.local, Weave Net
Advertising:
