This is the solution video for the Ingress controller lab.
So the first question is just an information we have deployed to application explore the set up and
they are in different places.
So let's head down to the terminal and on Cube, still get deployment's, dash, dash, all namespace.
And we can see that we have a few applications and they they're all in the app space names.
Click on talk and go to the next question, let us now deploy an English controller first just as to
create a new namespace where the Ingress controller will be deployed.
So let's copy the name of the namespace we created and we will go back to the Domhnall and I will create
and as our name space and the name of the namespace.
So the so the namespace has been created.
Let's move on.
The engine ingress controller requires a config map object, create a config object and the ingress
space.
Right now there is no data to be added to it.
Be an empty config map.
But it has to be in the correct news space and the name should be in the next configuration.
So let's use the imperative go on CubeSat or create s.m, which is short for conflict map and the name
of the conflict map, dash and space, and that should be it.
We are not adding any data to it.
For now.
It can be left empty.
Let's check and move on, the engineers in controller requires a service account, create a service
account in the English space, the name of the service account as ingress dash service account.
So let's copy that and let's use the combined capacity to create a save, which is short for service
account because the name of the service account and we have to provide name space.
So that's done as well.
It looks like automatically the rules and rule bindings for the service account has been created so
we can validate that this is just an information type question.
But to validate, we can come on such as Kubek till Dash and in GreenSpace get rules.
I can see that a new angrist rule has been created.
And let's check the roll bindings as well, so new and graceful binding has been created as well.
So click on OK and let's move on.
Let us now deploy the ingress controller, create a deployment using the file given.
So there is a file which is in the root directory called Ingres Controller Dot Yamal, it's what I want
replicas and the correct image and it should be indicate namespace.
So it looks like there is also an error in this deployment.
Files were allowed to try and fix it.
So let's first open the qualification file.
And straight away, we can see that the namespace is incorrect, it should be.
In Greece space, so that has been corrected and everything else seems to be OK for now, so let's try
to create it using Kupe still applied F and the name of the file, and looks like we are getting another
error and it looks like it has outlined 36 of the file.
So let's take Coolen 36 to navigate to that exact location on the file, and that is an error with the
indentation of the container port.
So let's fix that.
And again, try to create looks like there is yet another problem with this file.
No matches for the deployment and looks like the AP version is wrong.
So let's change that to apps we want.
So this is on version one, not one that as of this recording, so let's correct that and now our deployment
is successful.
The Ingress controller has been deployed now let us now create a service to make and increase available
to external users so we have these back on the right.
The name of the service should be ingress.
It should use type node, put the port as ATC, as the target port, and it should use an output of
three zero zero eight zero.
And of course, it should make use of the correct selector to be able to have endpoints points on the
deployment that we just created.
So let's create the service, let's use Kubica Dash and increase space Expo's deployment and the name
of the deployment, the name of the service, which should be ingress.
Let's also specify the report, which should be at.
And the target board, which is also at.
And we'll specify the type to be known put.
And then we'll make use of the dry run as equal to client feature so as not credos object natural Yamal
to generate a yellow file called Ingress Service Dot Yagmur.
Now, let's update this file and we'll predominantly add the note board, which should be.
Also, we have to set the namespace, even though we specified it and the come on, it did not.
Reflect on the file, so let's add that first and then next we'll add the note board, which according
to the question has to be said to.
Three zero zero eight zero.
So let's copy that.
And everything else seems to be OK, this letter is automatically created from the imperative, come
on, because we are exposing the deployment.
So now let's create the service using cube steel applied have increased our service, not YAML.
Now, let's get the service and looks like it has been created correctly with the type norpoth.
Now, we had to create the ingress resource to make the applications available at slash and slash watch
on all of the Ingress service.
And all these specifications have been provided on the right.
And it has to be created in the app space namespace, and to do this will rely on the equivalent documentation.
So let's go to documentation and on the search bar, let's search for ingress.
Click on the Ingress tab and we can copy the Ingress resource from the template provided here, so let's
create a new file.
Called Ingres National Resource Dimo.
And will paste the, uh, the template here and now let's go back and make sure that we change the definition
file in accordance to the question.
So a namespace we know that should be in the F space.
Rest of the things.
Let's copy from the questions or the name.
Of the injuries, it can be anything.
It doesn't specify it and the question, so let's make sure that we change the other field.
So let's seize the back in part to slash where for our first increase resource, the service name,
let's delete this and put it as a wire service in accordance to the service.
And similarly, we'll also have to add the second resource.
And for that, first, let's get the service description for the remaining two services.
We we've already added the rest of us and the second one as we do a service, which is also running
on Port AT&T.
So I'm just going to copy the back end definition the parts, and we'll copied and pasted onto the same
file and make changes as necessary for our radio service.
So let's go back to the V.I. editor for the same file and paste the.
Back in definition that we just copied, but will make changes to the fields here.
It should be video service and the parts should be.
Watch.
All right, so that looks all right.
Everything seems to be set up correctly, so let's use cube steel applied F and the local configuration
file for ingress resource and looks like the ingress has been created successfully.
And we can use Cube, Ctrl, Dash and.
App space and describe the new ingress so that we just created and here we can see that we have to back
in parts Foursquare, which is pointing to the weather service on both AT&T and the slash watch service,
which is a part which is pointing to DVD service at outport.
So that looks correct.
So let's click on Ingress and append the parts, which is where it is working, and let's change it
to slash watch, which is working as well.
So things looks to be correct.
Let's validate.
And we have already done this, we have already checked the increased resources working correctly by
accessing these parts on the Web so we can just click on OK.
And that was the last question for the SLAPP.
Thank you for joining me.
I'll see you in the next one.