![kubernetes same docker ip address kubernetes same docker ip address](https://cdn-images-1.medium.com/fit/t/1600/480/1*JqSLd3cPv14BWDtE7YEcRA.png)
If you would like to try it by yourself, you may always take a look at my source code. It provides DNS discovery for Kubernetes clusters connected by Submariner.
![kubernetes same docker ip address kubernetes same docker ip address](https://www.claudiokuenzler.com/graph/news/900-submariner-cross-cluster-communication.png)
Service discovery is based on the Lighthouse project. Then we run Submariner “agents” on both clusters. We run the Submariner Broker on the c1 cluster. The architecture of our example system is visible below. The Broker component facilitates the exchange of metadata information between Submariner gateways deployed in participating Kubernetes clusters. All the members may communicate directly with each other. Basically, a member is a Kubernetes cluster that is a part of the Submariner cluster. It runs a single, central broker and then joins several members to this broker. Since it is a relatively new tool you may have no touch with it. The caller-service application communicates with the callme-service application directly without using Kubernetes Ingress. The caller-service application is running on the c1 cluster, while the callme-service application is running on the c2 cluster. Also, there are two Kubernetes clusters c1 and c2 created using Kind. We have two applications caller-service and callme-service.
![kubernetes same docker ip address kubernetes same docker ip address](https://ronaknathani.com/blog/2020/08/how-a-kubernetes-pod-gets-an-ip-address/kubelet-cri-cni-flowchart.png)
Let’s perform a quick brief of our architecture. It enables direct networking between pods and services in different Kubernetes clusters, either on-premises or in the cloud. It is a tool originally created by Rancher. We should treat such clusters as two Kubernetes clusters running in different networks. Of course, it is not possible by default. Our goal in this article is to establish direct communication between pods running in two different Kubernetes clusters created with Kind. All these containers are running in the same Docker network kind. Each Kubernetes node is a separated Docker container. Kind ( Kubernetes in Docker) is a tool for running local Kubernetes clusters using Docker containers.
#KUBERNETES SAME DOCKER IP ADDRESS HOW TO#
In this article, you will learn how to create multiple Kubernetes clusters locally and establish direct communication between them with Kind and Submariner.