Now when you have a look at this big picture
at this Kubernetes architecture
which you in the end will set up
and with which Kubernetes will help you,
there is an important differentiation to make.
There are certain things Kubernetes will do for you,
but there also are aspects and things you need to do
in advance in order to then use Kubernetes.
So you need to provide a certain environment
in which Kubernetes is able to run.
And the very important thing you as the developer
or as the administrator have to do,
is you have to create and set up the cluster
and the worker nodes and the master node
on which Kubernetes is then installed and does its thing.
You have to do that.
You have to install all the Kubernetes software
on these nodes.
So on these machines which are part of your cluster.
And you have to configure all these things Kubernetes needs.
Depending on the cloud provider you might be using,
you also might need to set up extra resources
your Kubernetes cluster might need eventually.
Like a load balancer or certain filesystems services.
And we're going to have a look at that
throughout the next sections, of course.
I will show you how to set up
both a local testing environment on your local machine,
as well as to set up
the required resources on AWS as an example.
You just have to be aware
of the fact that you need to prepare the cluster.
But even though this might sound very challenging right now,
you will learn throughout this course
that it's actually quite easy.
Because both for local development
as well as with AWS as an example,
you get certain tools and services
which make creating that cluster very important.
It is important to understand though that Kubernetes
will not set up these resources.
Instead Kubernetes will use these resources.
Once it is installed and set up,
Kubernetes will manage these pods.
So these things, these units, which contain your containers.
It will create them, automatically distribute them
to take advantage of the available resources.
It will monitor and restart them if they fail.
It will manage the running deployment.
It will ensure that it runs smoothly and that it stays up
and running, and it will manage all of that for you.
It will start the containers for you.
As I said earlier it's like Docker Compose,
just for deploying your containers.
Where Docker Compose kind of struggles with that,
Kubernetes is really geared towards that.
And therefore it will do all of that.
But just as Docker Compose
doesn't configure your local computer.
It doesn't install Docker there.
It doesn't set up your local computer at all.
It just uses your local computer to then start containers
just as Docker compose does that locally.
Kubernetes also needs a certain environment
to do that on remote machines.
So that's an important differentiation to make.
And I will show you both;
how to set up a deployment with Kubernetes
and how to configure it so that it does manage
your containers for you, and how to set up a cluster.
I just want you to be aware
of the fact that this big picture which I'm showing you
requires some work from your side as well.
That Kubernetes will not create that cluster.
It will just use it.
But with that, let's dig deeper
into the worker and monster notes to take a
closer look at what exactly Kubernetes will do in there.