This is the solution we do for the demon sets a lab so for the first question we have to find out the
total number of demon sets created and all named spaces so let's go to the terminal and run cube deal.
Get the S which is short for Neiman sets and we'll use dash dash all these spaces and here you can see
that there are two demon sets one for Q proxy and the other one for.
We've met
and both of them are in the cube system namespace
with names faces are the demon sets and so we already check that it's in cubes of some namespace
which of the below is a demon set.
So we already check that as well we net as a set and the rest of them are not
on how many nodes are the parts should you buy the demon said CU proxy.
So as per the definition the demon set will be created on all the nodes in the cluster.
But let's take that anywhere we'll run cube it will get nodes that are two nodes in this cluster and
next Let try cube deal dash and cube system get ports and grep for Q proxy
and we have two ports.
Let's send that a little further by using the white to show the different nodes in which the ports are
scheduled.
So here you can see that it's schedule on Master and nodes or 1 so the answer is to
what is the image used by the port deployed by D.
We have net demon set
so to do this we will run cube CDL dash and cube system describe Newman said we have net and we can
grab for the image so you can see there are two images because it gives us two containers but we can
see which one is present and the option
so we have the Vive cube.
Two point six George Soros.
So that's the correct answer.
Deploy a demon set forth through Andy logging and use these given specification so the name of the demon
set us elastic search so we can use the cube when it is documentation for this.
So just look up a demon set and the documentation and that is an example which you can use if you want
to create the demon set.
You can also copy some of the fields from the documentation but there is also another way to do this
one we'll see that in just a moment so another way to do it is to use cube steel create deployment give
the name of the deployment or in this case the daemon set which is the last six search and provide the
image name which is flowing the elastic search one point to zero and will make use of the dash dash
dry run dash or Yama and redirect it to a file.
So we are not essentially creating the deployment.
We are just creating a Yammer format which we will edit later to creator and even set so here.
The file is elastic not Yama.
And now let's go into the file using we I text editor and change the kind from deployment to daemon
set and there are a couple of other fields which we will edit as well but this is my strict to create
a demon set because there's no imperative way to do it so next let's see the replicas too.
Let's delete that field.
Yeah but before that let's put the namespace as cubes assume because that's expected for the question.
Delete the replicas field delete the strategy because a demon that does not use a strategy and then
delete any other extra field that's not required.
So this looks all right.
You can compare it with the documentation as well.
So essentially what you can do is in this case we have to add the namespace but remove the replicas
and the strategy change the kind to daemon set and you should be good to go
see the file and create the daemon said using cubes still apply that Sheriff elastic ammo there you
go the demon that has been created.
We can check the status using cube teal dash and cube system get even set
let's check the answer.
That was the last question.
The final seven question is just an information so we will be using complex demon sets later in the
course to click okay and blab as John thank you for joining me in this video.
I'll see you and the next one.