Contents
- 1 What happens when the Kubernetes master fails?
- 2 How Kubernetes pods talk to each other?
- 3 How do I permanently delete pods in Kubernetes?
- 4 What happens if ETCD goes down Kubernetes?
- 5 How is pod to POD Communication done in node1?
- 6 Can a backend pod communicate with a frontend pod?
- 7 Do you need a virtual network for pods?
What happens when the Kubernetes master fails?
After failing over one master node the Kubernetes cluster is still accessible. Even after one node failed, all the important components are up and running. The cluster is still accessible and you can create more pods, deployment services etc.
How Kubernetes pods talk to each other?
In Kubernetes, pods can communicate with each other a few different ways: Containers in the same Pod can connect to each other using localhost , and then the port number exposed by the other container. A container in a Pod can connect to another Pod using its IP address.
How do you troubleshoot Kubernetes pods?
There are four useful commands to troubleshoot Pods:
- kubectl logs is helpful to retrieve the logs of the containers of the Pod.
- kubectl describe pod is useful to retrieve a list of events associated with the Pod.
How do I permanently delete pods in Kubernetes?
Deleting a StatefulSet You can delete a StatefulSet in the same way you delete other resources in Kubernetes: use the kubectl delete command, and specify the StatefulSet either by file or by name. You may need to delete the associated headless service separately after the StatefulSet itself is deleted.
What happens if ETCD goes down Kubernetes?
If the majority of etcd members have permanently failed, the etcd cluster is considered failed. In this scenario, Kubernetes cannot make any changes to its current state. Although the scheduled pods might continue to run, no new pods can be scheduled.
How do you check connection between pods?
To find the cluster IP address of a Kubernetes pod, use the kubectl get pod command on your local machine, with the option -o wide. This option will list more information, including the node the pod resides on, and the pod’s cluster IP. The IP column will contain the internal cluster IP address for each pod.
How is pod to POD Communication done in node1?
Pod-to-Pod communication (on same or across hosts) happens through ARP and L2 switching. We could use bridge CNI plug-in to reuse a L2 bridge for pod containers with the below configuration on node1 (note /16 subnet).
Can a backend pod communicate with a frontend pod?
In my case I have two pods: frontend and backend, both have different containers. I want my frontend pod to communicate with the backend pod but I don’t want to use backend pod’s IP ( i.e. hard coded). Is it possible through services? matt. Is it possible through services? Yes, services are the recommended way to handle this.
Can a node talk to a pod in Kubernetes?
So from above, Kubernetes requirements following communication paths must be established by the network. Nodes should be able to talk to all pods. For e.g. 192.168.1.100 should be able to reach 10.1.1.2, 10.1.1.3, 10.1.2.2 and 10.1.2.3 directly (without NAT) A Pod should be able to communicate with all nodes.
Do you need a virtual network for pods?
Similarly, Pods should be able to reach any node as well. We will need host routes in the nodes set such that Pods and nodes can talk to each other. Since inter host Pod-to-Pod traffic should not be visible in the underlay, we need a virtual/logical network that is overlaid on the underlay.