1

00:00:00,570 --> 00:00:04,170

This is the solution video for the Ingress controller lab.



2

00:00:06,610 --> 00:00:12,820

So the first question is just an information we have deployed to application explore the set up and



3

00:00:12,820 --> 00:00:14,530

they are in different places.



4

00:00:15,750 --> 00:00:23,730

So let's head down to the terminal and on Cube, still get deployment's, dash, dash, all namespace.



5

00:00:26,460 --> 00:00:33,720

And we can see that we have a few applications and they they're all in the app space names.



6

00:00:36,740 --> 00:00:43,760

Click on talk and go to the next question, let us now deploy an English controller first just as to



7

00:00:43,760 --> 00:00:47,470

create a new namespace where the Ingress controller will be deployed.



8

00:00:48,990 --> 00:00:57,180

So let's copy the name of the namespace we created and we will go back to the Domhnall and I will create



9

00:00:57,180 --> 00:01:01,320

and as our name space and the name of the namespace.



10

00:01:01,320 --> 00:01:04,140

So the so the namespace has been created.



11

00:01:04,590 --> 00:01:05,400

Let's move on.



12

00:01:07,080 --> 00:01:13,440

The engine ingress controller requires a config map object, create a config object and the ingress



13

00:01:13,440 --> 00:01:13,970

space.



14

00:01:14,820 --> 00:01:17,250

Right now there is no data to be added to it.



15

00:01:17,460 --> 00:01:19,050

Be an empty config map.



16

00:01:21,010 --> 00:01:26,710

But it has to be in the correct news space and the name should be in the next configuration.



17

00:01:28,730 --> 00:01:34,520

So let's use the imperative go on CubeSat or create s.m, which is short for conflict map and the name



18

00:01:34,520 --> 00:01:38,130

of the conflict map, dash and space, and that should be it.



19

00:01:38,150 --> 00:01:39,850

We are not adding any data to it.



20

00:01:40,100 --> 00:01:40,520

For now.



21

00:01:40,530 --> 00:01:41,900

It can be left empty.



22

00:01:43,750 --> 00:01:50,560

Let's check and move on, the engineers in controller requires a service account, create a service



23

00:01:50,560 --> 00:01:56,800

account in the English space, the name of the service account as ingress dash service account.



24

00:01:57,160 --> 00:02:04,240

So let's copy that and let's use the combined capacity to create a save, which is short for service



25

00:02:04,240 --> 00:02:09,690

account because the name of the service account and we have to provide name space.



26

00:02:10,330 --> 00:02:11,640

So that's done as well.



27

00:02:19,550 --> 00:02:24,020

It looks like automatically the rules and rule bindings for the service account has been created so



28

00:02:24,020 --> 00:02:27,940

we can validate that this is just an information type question.



29

00:02:29,140 --> 00:02:35,650

But to validate, we can come on such as Kubek till Dash and in GreenSpace get rules.



30

00:02:39,440 --> 00:02:42,110

I can see that a new angrist rule has been created.



31

00:02:43,320 --> 00:02:48,760

And let's check the roll bindings as well, so new and graceful binding has been created as well.



32

00:02:49,410 --> 00:02:51,300

So click on OK and let's move on.



33

00:02:52,470 --> 00:02:57,330

Let us now deploy the ingress controller, create a deployment using the file given.



34

00:02:59,690 --> 00:03:06,440

So there is a file which is in the root directory called Ingres Controller Dot Yamal, it's what I want



35

00:03:06,440 --> 00:03:10,020

replicas and the correct image and it should be indicate namespace.



36

00:03:10,040 --> 00:03:13,130

So it looks like there is also an error in this deployment.



37

00:03:13,130 --> 00:03:15,050

Files were allowed to try and fix it.



38

00:03:17,950 --> 00:03:21,400

So let's first open the qualification file.



39

00:03:22,970 --> 00:03:27,620

And straight away, we can see that the namespace is incorrect, it should be.



40

00:03:29,560 --> 00:03:38,740

In Greece space, so that has been corrected and everything else seems to be OK for now, so let's try



41

00:03:38,740 --> 00:03:44,920

to create it using Kupe still applied F and the name of the file, and looks like we are getting another



42

00:03:44,920 --> 00:03:49,480

error and it looks like it has outlined 36 of the file.



43

00:03:51,480 --> 00:04:00,030

So let's take Coolen 36 to navigate to that exact location on the file, and that is an error with the



44

00:04:00,030 --> 00:04:02,430

indentation of the container port.



45

00:04:02,460 --> 00:04:03,410

So let's fix that.



46

00:04:04,080 --> 00:04:10,000

And again, try to create looks like there is yet another problem with this file.



47

00:04:10,500 --> 00:04:14,110

No matches for the deployment and looks like the AP version is wrong.



48

00:04:14,970 --> 00:04:18,420

So let's change that to apps we want.



49

00:04:22,840 --> 00:04:29,470

So this is on version one, not one that as of this recording, so let's correct that and now our deployment



50

00:04:29,470 --> 00:04:30,430

is successful.



51

00:04:32,770 --> 00:04:41,230

The Ingress controller has been deployed now let us now create a service to make and increase available



52

00:04:41,230 --> 00:04:44,610

to external users so we have these back on the right.



53

00:04:44,620 --> 00:04:46,470

The name of the service should be ingress.



54

00:04:46,480 --> 00:04:52,750

It should use type node, put the port as ATC, as the target port, and it should use an output of



55

00:04:52,750 --> 00:04:54,070

three zero zero eight zero.



56

00:04:54,070 --> 00:04:59,740

And of course, it should make use of the correct selector to be able to have endpoints points on the



57

00:04:59,740 --> 00:05:01,240

deployment that we just created.



58

00:05:03,020 --> 00:05:10,760

So let's create the service, let's use Kubica Dash and increase space Expo's deployment and the name



59

00:05:10,760 --> 00:05:15,410

of the deployment, the name of the service, which should be ingress.



60

00:05:19,260 --> 00:05:22,560

Let's also specify the report, which should be at.



61

00:05:24,640 --> 00:05:28,480

And the target board, which is also at.



62

00:05:29,980 --> 00:05:32,590

And we'll specify the type to be known put.



63

00:05:34,560 --> 00:05:42,030

And then we'll make use of the dry run as equal to client feature so as not credos object natural Yamal



64

00:05:42,030 --> 00:05:46,350

to generate a yellow file called Ingress Service Dot Yagmur.



65

00:05:47,580 --> 00:05:53,610

Now, let's update this file and we'll predominantly add the note board, which should be.



66

00:05:57,320 --> 00:06:02,360

Also, we have to set the namespace, even though we specified it and the come on, it did not.



67

00:06:03,420 --> 00:06:10,200

Reflect on the file, so let's add that first and then next we'll add the note board, which according



68

00:06:10,200 --> 00:06:13,230

to the question has to be said to.



69

00:06:14,370 --> 00:06:15,870

Three zero zero eight zero.



70

00:06:16,140 --> 00:06:17,160

So let's copy that.



71

00:06:19,730 --> 00:06:24,830

And everything else seems to be OK, this letter is automatically created from the imperative, come



72

00:06:24,830 --> 00:06:26,930

on, because we are exposing the deployment.



73

00:06:28,260 --> 00:06:33,690

So now let's create the service using cube steel applied have increased our service, not YAML.



74

00:06:37,480 --> 00:06:44,950

Now, let's get the service and looks like it has been created correctly with the type norpoth.



75

00:06:47,550 --> 00:06:54,150

Now, we had to create the ingress resource to make the applications available at slash and slash watch



76

00:06:54,150 --> 00:06:56,340

on all of the Ingress service.



77

00:06:59,220 --> 00:07:03,090

And all these specifications have been provided on the right.



78

00:07:05,090 --> 00:07:11,320

And it has to be created in the app space namespace, and to do this will rely on the equivalent documentation.



79

00:07:11,330 --> 00:07:15,950

So let's go to documentation and on the search bar, let's search for ingress.



80

00:07:16,920 --> 00:07:24,390

Click on the Ingress tab and we can copy the Ingress resource from the template provided here, so let's



81

00:07:24,390 --> 00:07:25,350

create a new file.



82

00:07:28,490 --> 00:07:32,240

Called Ingres National Resource Dimo.



83

00:07:33,570 --> 00:07:44,370

And will paste the, uh, the template here and now let's go back and make sure that we change the definition



84

00:07:44,370 --> 00:07:45,890

file in accordance to the question.



85

00:07:47,430 --> 00:07:50,400

So a namespace we know that should be in the F space.



86

00:07:51,210 --> 00:07:52,020

Rest of the things.



87

00:07:52,020 --> 00:07:54,210

Let's copy from the questions or the name.



88

00:07:56,320 --> 00:07:58,970

Of the injuries, it can be anything.



89

00:07:58,990 --> 00:08:05,170

It doesn't specify it and the question, so let's make sure that we change the other field.



90

00:08:10,690 --> 00:08:18,910

So let's seize the back in part to slash where for our first increase resource, the service name,



91

00:08:19,210 --> 00:08:25,240

let's delete this and put it as a wire service in accordance to the service.



92

00:08:26,710 --> 00:08:30,070

And similarly, we'll also have to add the second resource.



93

00:08:30,070 --> 00:08:36,560

And for that, first, let's get the service description for the remaining two services.



94

00:08:36,730 --> 00:08:42,640

We we've already added the rest of us and the second one as we do a service, which is also running



95

00:08:42,640 --> 00:08:44,080

on Port AT&T.



96

00:08:45,870 --> 00:08:53,760

So I'm just going to copy the back end definition the parts, and we'll copied and pasted onto the same



97

00:08:53,760 --> 00:08:57,570

file and make changes as necessary for our radio service.



98

00:08:59,350 --> 00:09:05,560

So let's go back to the V.I. editor for the same file and paste the.



99

00:09:07,200 --> 00:09:12,060

Back in definition that we just copied, but will make changes to the fields here.



100

00:09:12,080 --> 00:09:16,620

It should be video service and the parts should be.



101

00:09:19,720 --> 00:09:20,230

Watch.



102

00:09:21,480 --> 00:09:23,220

All right, so that looks all right.



103

00:09:23,400 --> 00:09:32,310

Everything seems to be set up correctly, so let's use cube steel applied F and the local configuration



104

00:09:32,310 --> 00:09:37,740

file for ingress resource and looks like the ingress has been created successfully.



105

00:09:38,670 --> 00:09:40,950

And we can use Cube, Ctrl, Dash and.



106

00:09:42,000 --> 00:09:49,320

App space and describe the new ingress so that we just created and here we can see that we have to back



107

00:09:49,320 --> 00:09:56,400

in parts Foursquare, which is pointing to the weather service on both AT&T and the slash watch service,



108

00:09:56,400 --> 00:10:01,550

which is a part which is pointing to DVD service at outport.



109

00:10:02,140 --> 00:10:03,110

So that looks correct.



110

00:10:03,600 --> 00:10:13,200

So let's click on Ingress and append the parts, which is where it is working, and let's change it



111

00:10:13,200 --> 00:10:16,810

to slash watch, which is working as well.



112

00:10:16,830 --> 00:10:18,660

So things looks to be correct.



113

00:10:18,870 --> 00:10:19,920

Let's validate.



114

00:10:21,430 --> 00:10:27,190

And we have already done this, we have already checked the increased resources working correctly by



115

00:10:27,190 --> 00:10:32,390

accessing these parts on the Web so we can just click on OK.



116

00:10:32,410 --> 00:10:34,800

And that was the last question for the SLAPP.



117

00:10:34,870 --> 00:10:35,950

Thank you for joining me.



118

00:10:36,850 --> 00:10:38,110

I'll see you in the next one.