This is the solution video for the servers, Networking Lab. So the first question we have to identify
the network range of the nodes which are part of this cluster.
So in the terminal, let's run Kubek to get nodes or wide.
This will give us the IP address of both the north, so we have two nodes, Masra, another one, and
the internal IP address starts with one seventy to 17, zero twenty four and twenty seven.
So let us look at the side range for this network, which makes use of industry, as we saw in one of
the labs earlier, for a node to note communication.
And here we can see that it's using 16.
And it begins with 172 dots, 17, not zero, so most appropriate answer here is 117 to dot 17 or zero
zero, which is the exact network, and slash 16 as the Seiter.
What is the range of IP address configured for ports on this cluster?
So this is specifically for the port, not the nodes itself.
So to take this, we can we can see the configuration of the IV plug in port.
So I'm going to run Cube CTL log's.
For the evening at port and inside, we have a container called Veve, so if we open up the logs for
this, we should see the IP allocation range somewhere here.
So if you scroll to the very top, you see that epilog range.
Is set to.
Then today, 2.0 slashed 12.
So that's one way of doing it.
We can also look up at the configuration for we've but in this case, this is the most appropriate answer.
So we'll go with that.
What is the IP range configured for these services within the cluster?
So in this case, we are looking at services.
We have already checked node and ports.
So let's look at services for this.
Another easy way to do it is to check the address range, which is configured and like API server.
So I'm going to open up this definition file for Kuepper Server using Viator.
And if you scroll all the way to the bottom or in the command section, we should see the service address
range.
So here these service cluster IP range is standard 96 dot zero zero, slash 12.
So let's let that.
How many proxy ports are deployed in this cluster, so the proxy is typically Iran as a demon's head
as well.
So you can see that we have two parts running.
What type of proxy is proxy configured to use?
We know that by default it makes use of IP table genes, but we can validate that.
Again, let's look at the logs.
RFQ proxy, so let's select one of the pods here so we'll make use of the common cube CTO.
Nash and cube system logs and the Q proxy part.
So if you see the first line, it is assuming IAPT was proxy, so that's our answer.
And for the last question, we have to answer this, how does the scoop, when it is close to ensure
that a proxy pot runs on all nodes in the cluster?
So we already discussed that Q proxy Iran as a demon said, but we can validate that on the terminal
by Iran and Cuba, still get assets in the system namespace.
And here we can see that your proxy is in the list and it does not require us to decide parts of it
to our current and to already.
So the answer is using a demon set.
So that was the last question.
Thank you for joining me in this video.
Also in the next one.