Okay.
In this lab,
we will be installing Weave Net POD networking solution to the cluster
so let us first inspect the setup.
We've deployed an application called app.
Let's check that out.
Kubectl get PODs.
We have app and the status is container creating.
What is the state of the POD?
It's not running.
Still in a container creating state so it's not running.
Inspect why the POD is not running.
Let's do a kubectl describe POD app.
We see that it's failed to create a POD sandbox and network for POD,
network plugins, cni failed to set up POD.
Basically, it looks like there's a network issue.
The network plugin cni failed to teardown POD network.
It's not because it's faulty start, wrong image, or node failed,
it's because there's no network configured.
Let's deploy a view net networking solution to the cluster.
Let's do that now.
I remember to replace the default IP address
and subnet of Weave Net to 10.50.0.0/16.
Let's look at the Weave Net installation guide.
We're going to go to the Weave works
installation documentation,
and then we're going to use the installation guide here.
Basically, it's just the command that can help us install weave works.
Let's do that right now.
Now, one of the things that's mentioned here
is to use the IP range 10.50.0.0/16.
If you look at the solution given here,
we'll see that the reason that we're asking that to be done
is because the Weave Net default subnet
that it uses for the POD network is 10.32.0.0/12, and that will overlap
with the cluster IP range that's configured.
What we're going to do is we're going to specify
this IP allocation range,
which is a new range.
You have to add that at the end of this command like this.
We're going to copy this.
Paste it right here.
We're running the same kubectl apply command,
but at the end, we're appending this IP allocation range.
Let's give that a shot.
Now, let's check the status of the weave POD.
We see that the Weave Net POD is running.
Let's check the status of the app POD and the app POD is now running as well.
Okay.
That's successful.
This was a lab to just demonstrate the installation of a network solution
and that happens to be Weave in this case and because we've talked about weave,
but this could be anything.
From an exam perspective,
you don't really have to worry about going to the Weave documentation pages
because as part of the exam,
you're not allowed to go outside of the Kubernetes documentation pages,
so you can safely assume that it's going to be something
that's within the Kubernetes documentation pages.