This is the solution video for the multiple schedulers lab, so the first question, what is the name
of the pod that deploys the default, the scheduler and the environment?
So to find this, let us go to the Domhnall and type Kubasik, we'll get parts on the system namespace.
So that should you, as part of the control plane and as deployed and the collapse of some space, and
here you can see that the name of the scheduler is called Kupe Scheduler Master.
And this is deployed as a static port, so let's select that as our answer.
Was the image used to deploy the equivalent of scheduler and to find this field on our describe against
the port?
And let's use the clip, come on, and wait for the image.
And here we have the image, which is chaos or discord or I'll slash Kupe scheduler Beaujon one, not
one eight.
Next, we have to deploy an additional scheduler to the cluster using the specification on the right.
So it has to be deployed in the same namespace as well.
The name should be my scheduler.
It should have the custom scheduler name and it should be in the running street.
We can use the manifest file used by the Cupido to deploy the default the scheduler.
Secure Adam Tool deploys the scheduler on other controlled plane components by making use of manifest
file, which is by default and the sequence this manifest directly.
So let's go there first.
And here we have a file called Cube does do document.
So let's copy that.
And we'll copy that to the route, but we'll also rename the file to my dad's or document.
So now I'm back to slash food and let's edit our mind to learn of.
Before we make any changes, let's go to the Corners documentation and look at the official docs for
creating multiple schedules.
I'm just going to search for multiple scheduler.
And here we have a link that says Configure multiple Muslim communities.
So let's click on that and let's scroll down to the definition.
So here we have an example where the the scheduler or an additional governor, the scheduler has been
deployed, has been deployed as this deployment.
And here we have the definition for the second rule, binding sex, which we do not have to do in this
case because we are making use of the definition file, which we have copied from the benefits category,
which is when it is manifest.
We will not have to do any of these.
But let's go and check out the definition FIGLIA.
So here we have the command section for the containers and we can see that there are two options that
we have to consider.
One is the leader elect should be the default and then the scheduler name that we have to specify,
which is also in this case, where the scheduler.
So let's copy those two lines from here.
In fact, the relict command is already there, it is set to true, but we can't use that to follow.
So let's go all the way down
to the command section and I'm going to change it to false.
And it's this page.
You should the name should be mine.
I should look let's see the name of the pod to my right scheduler as well.
And while we're at it, let's also change the name of the container.
It's not necessary, but it does change it.
And everything else should be OK.
And in accordance with the documentation.
So let's go ahead and create this custom scheduler by the name of my scheduler.
You can see that the port has been created.
It's wrong to get parts of the tube system namespace again and the bottom, we can see that the Midas
scheduler part has been created and it doesn't enough running street.
So let's validate our answer.
So for the final question, the definition is given, use it to create a part with the new costume scheduler
and the definition is located at Slashdot and the next dashboard odioma.
So it should make use of the customary.
So here is our definition file.
So in order to make use of our customary law that we just created will add a new field under the special
section called Scheduler Name and the name of the scheduler.
Now, let's create this blog.
And let's take this tweet us using Kubasik, they'll get Pott's.
Does and contain accreting said.
I'm just using this watch command here just to make sure that it takes to see every two seconds, I
know it's already in I'm running state, so I'm going to control all of this.
And while we're at it, let's try and keep still.
Describe what?
Ingenix.
And here we can see that it has made use of the Midas scheduler to assign the part called the engine
next to another one, and it is now running shape.
So that should be the end of this solution.
We do.
Thank you for joining me and I'll see you in the next one.