Difference between revisions of "Kubernetes networking"
Jump to navigation
Jump to search
| Line 16: | Line 16: | ||
* [[Container Network Interface (CNI)]] | * [[Container Network Interface (CNI)]] | ||
* [[CoreDNS]] | * [[CoreDNS]] | ||
| − | * <code>[[ | + | * <code>[[kubectl proxy]]</code> |
| + | * <code>[[kubectl port-forward]]</code> | ||
* <code>[[vpc-cni]]</code> | * <code>[[vpc-cni]]</code> | ||
| − | + | ||
* <code>[[kind: NetworkPolicy]]</code> | * <code>[[kind: NetworkPolicy]]</code> | ||
* [[Service mesh]] | * [[Service mesh]] | ||
Revision as of 16:44, 1 December 2022
https://kubernetes.io/docs/concepts/cluster-administration/networking/
The Container Network Interface (CNI) plugin is selected by passing kubelet the --network-plugin=cni
Activities
- 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
Related terms
See also
- Tigera: Calico, Typha, Canal,
calicoctl, calico-kube-controllers, kind: BGPPeer - Ingress controllers, NGINX Ingress Controller,
minikube addons enable ingress,kubectl get ingress, kubectl get ingressclass, kubectl describe ingress,Ingress:, Ingress API, AWS Load Balancer Controller, Envoy Proxy, GKE Ingress, Kubernetes Gateway API,ingress.k8s.aws, ingresses.networking.k8s.io,kind: Ingress: (tls:, hosts:),SuccessfullyReconciled - 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:
