Hello and welcome to this lecture in this lecture.
We will discuss about networking in Cuba, Narus.
Let us look at the very basics of networking in Cuba, Natus.
We will start with a single node, Cuban and its cluster.
The node has an IP address, say it is 192 dot, 168 dot one or two.
In this case, this is the IP address we use to access the Cuban.
It is node SFH into it, et cetera.
On a side note, remember, if you're using a mini cube setup that I'm talking about, the IP address
of the mini cube virtual machine inside your hypervisor, your laptop may be having a different IP like
one eighty two the 168 or one dot 10.
So it's important to understand how your volumes are setup.
So on the single node, Coburn, it is cluster.
We have created a single pod, as you know, a pod hosts a container, unlike in the Docker world,
where an IP address is always assigned to a stock or container in the cabinet is world.
The IP address is assigned to a pod.
Each part in the carbonates gets its own internal IP address.
In this case, it's in the range TANDOOR to 44 series.
And the IP assigned to the pod is ten or 240, 4.0 or two.
So how is it getting this IP address when Khubani this is initially configured?
We create an internal private network with the address tendered to 40 forward or zeroed out zero and
all the parts are attached to it.
When you deploy multiple parts, they all get a separate IP assigned from this network.
The parts can communicate to each other through this IP, but accessing the other parts using this internal
IP address may not be a good idea as it's subject to change when parts are recreated.
We will see better ways to establish communication between parts in a while.
For now, it's important to understand how the internal networking works in Cupertino as.
So it's all easy and simple to understand when it comes to networking on a single note.
But how does it work when you have multiple nodes in your cluster?
In this case, we have two nodes running Cuban natives and they have IP addresses, 192, 168.
One or two and one dot three assigned to them.
Note that they are not part of the cluster yet.
Each of them has a single pod deployed, has discussed in the previous slide.
These parts are attached to an internal network and they have their own IP addresses assigned.
However, if you look at the internal network addresses, you can see that they are the same.
The two networks have an address 10 to 44 dot zero or zero, and the paths deployed have the same address
to.
This is not going to work well when the nodes are part of the same cluster.
The parts have the same IP addresses assigned to them, and that will lead to IP conflicts in the network.
Now, that's one problem when a it is cluster a setup.
Cuban.
And this does not automatically set up any kind of networking to handle these issues.
As a matter of fact, Cuban, it is, expects us to set up networking to meet certain fundamental requirements.
Some of these are that all the containers or pods in a Cuban Natus cluster must be able to communicate
with one another without having to configure net.
All nodes must be able to communicate with containers and all containers must be able to communicate
with the nodes in the cluster.
Cuban Notis expects us to set up a networking solution that meets these criteria.
Fortunately, we don't have to set it up all on our own as there are multiple pre-built solutions available.
Some of them are the Cisco FCI Networks, Psyllium, big cloud fabric, flannel Vilmer, NSX, T and
Kalikow.
Depending on the platform you're deploying your Kuban, it is Kluster on.
You may use one of these solutions.
For example, if you were setting up a carbonated cluster from scratch on your own systems, you may
use any of the solutions like Kalikow or flannel, etc..
If you were deploying on a V ember environment, NSX t may be a good option.
If you look at the play with Kades Labs, they use weave net as their networking solution.
So back to our cluster with the custom networking, either flannel or calico setup.
It now manages the networks and eyepiece in my notes and assigns a different network address for each
network in the node.
This creates a virtual network of all pods and nodes where they are all assigned a unique IP address.
And by using simple routing techniques, the cluster networking enables communication between the different
paths or nodes to meet the networking requirements of Cuban.
This does all the paths.
Now can communicate to each other using the assigned IP address.