![]() Two containers say apache and mysql running on the same Pod, can talk to each other using "localhost". Containers running in Kubernetes Pods share the same network namespace, i.e.Each Kubernetes Pod gets a Pod IP that is reachable from all the nodes that form the Kubernetes cluster.Kubernetes Pods have some very useful properties: A pod models an application-specific “logical host” - it contains one or more application containers which are relatively tightly coupled - in a pre-container world, they would have executed on the same physical or virtual machine. Pods are always co-located and co-scheduled, and run in a shared context. Kubernetes Podsįrom the Kubernetes website, a Pod is described in the following words:Ī pod (as in a pod of whales or pea pod) is a group of one or more containers (such as Docker containers), the shared storage for those containers, and options about how to run the containers. Each step in the workflow is a Kubernetes Pod. Our infrastructure runs on top of Kubernetes, and we also allow our users to create workflows that are composed of multiple steps. In this post, we will talk about how running the Docker daemon inside a Docker container, Docker-inside-Docker (DinD), works better with Kubernetes Pods as compared to DooD (If these terms are unfamiliar please check out the previous post). In the previous post, we examined some of the issues of using the host Docker daemon socket, Docker-outside-of-Docker (DooD), inside containers running on a CI/CD system.
0 Comments
Leave a Reply. |