Difference between revisions of "Kubernetes networking"
Jump to navigation
Jump to search
| (2 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
* [[Calico]] | * [[Calico]] | ||
* [[Flannel]] | * [[Flannel]] | ||
| + | * [[Cilium]] | ||
| + | * [[Multus CNI]] | ||
* [[Kubernetes ExternalDNS]] | * [[Kubernetes ExternalDNS]] | ||
| Line 22: | Line 24: | ||
== Related terms == | == Related terms == | ||
| + | * [[Network policies]] | ||
* [[AWS EKS Addons]]: <code>[[vpc-cni]]</code> | * [[AWS EKS Addons]]: <code>[[vpc-cni]]</code> | ||
Latest revision as of 10:06, 23 April 2024
https://kubernetes.io/docs/concepts/cluster-administration/networking/
The Container Network Interface (CNI) plugin is selected by passing kubelet the --network-plugin=cni
Activities[edit]
- Create a pod network:
kubeadm init --pod-network-cidr=10.244.0.0/16 - Understand host networking configuration on the cluster nodes (CKA v1.23, CKA v1.24, CKA v1.25)
- Understand connectivity between Pods (CKA v1.23, CKA v1.24, CKA v1.25)
- Know how to configure and use CoreDNS (CKA v1.23, CKA v1.24, CKA v1.25)
- CKA: Troubleshoot networking
- CKA: Choose an appropriate container network interface plugin
- Read https://kubernetes.io/blog/2022/05/23/service-ip-dynamic-and-static-allocation/
- Exposing an External IP Address to Access an Application in a Cluster:
kubectl expose deployment
Related terms[edit]
See also[edit]
- 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:
