1

00:00:00,210 --> 00:00:08,190

This is the solution video for the Ingress lab, so there are a few deployments for Ingress controller



2

00:00:08,190 --> 00:00:12,610

and resources and other applications in this cluster, which are in different names, pieces of us.



3

00:00:12,630 --> 00:00:13,710

We'll explore them.



4

00:00:15,540 --> 00:00:22,770

So to do that, let's run Cuba, still get deployment's, dash, dash, all naem space's.



5

00:00:26,190 --> 00:00:32,760

And we see that there are a couple of names here, the first one is called Cap Space, which has a few



6

00:00:32,760 --> 00:00:34,410

deployments for your application.



7

00:00:35,920 --> 00:00:39,970

And then there is the English space, which has the Ingenix English controller.



8

00:00:42,060 --> 00:00:48,720

So let's go to the next question, which namespace is the Ingress controller deployed and we know that



9

00:00:48,720 --> 00:00:50,520

it's in the ingress space.



10

00:00:51,930 --> 00:00:54,810

What is the name of the Ingress controller deployment?



11

00:00:55,440 --> 00:00:57,840

We know that it's Ingenix Ingress controller.



12

00:01:00,260 --> 00:01:05,630

Britney Spears are the applications deployed and we already saw that it's in the app space.



13

00:01:07,190 --> 00:01:13,550

How many applications are deployed in the app space namespace, so let's count, there are in total



14

00:01:13,550 --> 00:01:16,850

three deployments, so the answer is three.



15

00:01:18,680 --> 00:01:26,030

Which means space is the increased resource deployed, and so to find this, let's run Cuba, still



16

00:01:26,900 --> 00:01:30,110

get ingress and dash, dash, all limp space's.



17

00:01:31,170 --> 00:01:35,280

And we see that it is deployed in the app space namespace.



18

00:01:41,450 --> 00:01:43,730

What is the name of the Ingress resource?



19

00:01:43,760 --> 00:01:47,060

We know that it is in Greece where watch from the previous command.



20

00:01:49,410 --> 00:01:56,970

What as the host country good on the Ingress resource to find us will run Cukier, describe Ingres.



21

00:01:58,590 --> 00:02:04,800

Or we can even find it out from the previous comment, it's set to Star, which is all Dehousse.



22

00:02:07,790 --> 00:02:17,780

What back in those days were part on the increased country godwit, and for this we definitely have



23

00:02:17,780 --> 00:02:19,910

to make use of cubical describe.



24

00:02:21,960 --> 00:02:28,860

And let's use the national space for the new space and we'll describe ingress called ingress where watch



25

00:02:30,060 --> 00:02:38,370

and we see that the back end is where, service for where and for what it is we do service.



26

00:02:40,050 --> 00:02:42,540

So let's select where service.



27

00:02:47,290 --> 00:02:49,000

Which is the answer in this case.



28

00:02:50,690 --> 00:02:56,090

At what part as the video streaming application made available on the ingress?



29

00:02:57,720 --> 00:03:04,350

So if you see the back in part, it is slash watch, which makes use of the video service.



30

00:03:05,930 --> 00:03:07,100

The answer should be.



31

00:03:08,980 --> 00:03:09,610

Watch.



32

00:03:12,720 --> 00:03:19,260

If the requirement does not match any of the country parts, which service are what services are the



33

00:03:19,260 --> 00:03:20,490

requests forwarded?



34

00:03:21,790 --> 00:03:27,910

So this will go to the default back end, which is configured, the default SCDP back end would be the



35

00:03:27,910 --> 00:03:28,510

service.



36

00:03:32,480 --> 00:03:37,760

Now view the ingress service using the tab at the top of the terminal, which pays, do you see?



37

00:03:39,010 --> 00:03:41,740

So let's click on the tab called Ingres.



38

00:03:42,740 --> 00:03:47,600

And right now, we are getting an SCDP four or four Web page.



39

00:03:49,160 --> 00:03:55,880

So it looks like it's not working it so for or for error, which is the answer to the application by



40

00:03:55,880 --> 00:03:57,970

appending where and slash watch.



41

00:03:57,980 --> 00:04:00,590

So let's add that to the end of the URL here.



42

00:04:01,840 --> 00:04:05,790

Hogwash, and you can see that we have the video service.



43

00:04:07,260 --> 00:04:12,600

You are requested to change the Urals at with the applications are made available, so we have to make



44

00:04:12,600 --> 00:04:20,330

the back and change the part to stream and sort of currently set to watch.



45

00:04:21,030 --> 00:04:22,890

So let's change that.



46

00:04:27,470 --> 00:04:33,240

To do this, let's on Cuba's media and our space, get ingress and egress.



47

00:04:33,260 --> 00:04:37,940

Where was the actual Yamal and redirected to a file called In Restored Giammo.



48

00:04:39,080 --> 00:04:46,820

Now, let's edit this configuration file and we'll change the back in part for the video service to



49

00:04:47,570 --> 00:04:48,320

stream.



50

00:04:50,870 --> 00:04:58,550

Once this is done, let's use cubicle dash in our space, delete ingress to delete the current configuration,



51

00:04:58,550 --> 00:05:03,710

and let's apply and recreate it from our configuration file.



52

00:05:04,640 --> 00:05:14,930

So now if your should no longer work with this watch bot, but if you change it to stream, we are able



53

00:05:14,930 --> 00:05:22,730

to see the webpage so that it's successful and we've already done this, but we're able to view it with



54

00:05:22,730 --> 00:05:24,920

this large stream added to the euro.



55

00:05:26,060 --> 00:05:32,000

Now the next question as a user is trying to view these Ertuğrul on the English service.



56

00:05:32,000 --> 00:05:33,890

Which page would you see?



57

00:05:35,310 --> 00:05:43,290

So there is no slash eat, can't eat pot configured, so it should go to the SCDP default back in.



58

00:05:44,430 --> 00:05:46,200

So we are getting the Arrow page.



59

00:05:49,130 --> 00:05:55,850

Due to the increased demand, your business decides to take on a new venture, you acquired a food delivery



60

00:05:55,850 --> 00:05:59,360

company, their applications have been migrated over to the cluster.



61

00:05:59,840 --> 00:06:03,980

First inspect the new applications which are deployed in the cluster.



62

00:06:06,080 --> 00:06:12,770

So let's try and still get deployment's on namespace, and you see that there is a new deployment called



63

00:06:12,770 --> 00:06:16,220

Web App Dashboard and the app space namespace.



64

00:06:19,160 --> 00:06:21,140

And now let's also take the service.



65

00:06:23,120 --> 00:06:30,830

And we see that our food service has been created as well in the same name space.



66

00:06:36,820 --> 00:06:42,550

You are requested to add a new part to the Congress to make the food delivery application available



67

00:06:42,550 --> 00:06:49,810

to your customers so the configuration is given on the right to make use of it as the board.



68

00:06:50,530 --> 00:06:54,220

And we already inspected the deployment and the services.



69

00:06:56,970 --> 00:07:03,030

So let's update the configuration file that we created earlier, we are going to add another back end.



70

00:07:08,620 --> 00:07:11,740

So in this case, the new back end would be for the food service.



71

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

So let's add that underneath as a new ORAY.



72

00:07:17,470 --> 00:07:22,750

And just copy pasting, the previous result will just make changes to the service name, the food service,



73

00:07:23,320 --> 00:07:27,670

the service port is exactly as it is, and the parts should be eat.



74

00:07:29,620 --> 00:07:36,730

Once this is done, we'll do the same step as before, we'll delete the current ingress resource and



75

00:07:36,730 --> 00:07:39,490

recreate it from the local configuration file.



76

00:07:40,470 --> 00:07:43,230

Now, if you're afraid, you're able to create a webpage.



77

00:07:46,090 --> 00:07:48,330

We've already done that, so let's move on.



78

00:07:48,730 --> 00:07:54,640

A new payment service has been introduced since it is critical the new application has deployed its



79

00:07:54,640 --> 00:07:55,650

own namespace.



80

00:07:56,200 --> 00:08:00,280

So let's first inspect the new deployment and a new namespace.



81

00:08:03,230 --> 00:08:08,300

So, yeah, let's run the same command as before, and now we can see that a new deployment by the name



82

00:08:08,300 --> 00:08:10,790

of baby is in the critical space.



83

00:08:16,820 --> 00:08:25,100

And let's run the deployments and services them together on the critical space namespace and we see



84

00:08:25,100 --> 00:08:29,780

that build our service has also been created and reporters eat to to.



85

00:08:34,880 --> 00:08:40,780

All right, so we know that it is in the critical space, what is the name of the deployment?



86

00:08:41,900 --> 00:08:45,410

So we know that it is webapp B.



87

00:08:52,410 --> 00:08:59,250

Now, you're now requested to make the new application available at Igby, so let's create a new Ingres



88

00:08:59,250 --> 00:08:59,970

resource.



89

00:09:02,110 --> 00:09:10,060

So they just copy the current YAML file and rename it to new file called Critical Dot Giammo, and the



90

00:09:10,060 --> 00:09:15,840

part should be Igby and it should make use of the appropriate services that we have already inspected.



91

00:09:15,850 --> 00:09:23,350

So let's make the change to this new file that we copied and scroll all the way to the spec section.



92

00:09:25,590 --> 00:09:30,690

Yeah, and first, we have to change the name space to critical space, because that's where the deployments



93

00:09:30,690 --> 00:09:32,040

and the services are created.



94

00:09:32,610 --> 00:09:37,440

It's also changed the name of the ingress resource to ingress be.



95

00:09:38,860 --> 00:09:43,030

Next, let's update the backhands, so this should just have one back in.



96

00:09:44,470 --> 00:09:46,240

Let's get rid of the other two.



97

00:09:47,340 --> 00:09:56,280

And the service name should be very happy, the the service name should be paid service the borders



98

00:09:56,420 --> 00:09:58,720

to it too, and the parts should be slashed.



99

00:09:58,740 --> 00:09:59,040

Pay.



100

00:10:01,830 --> 00:10:04,050

So that was done so we can now.



101

00:10:06,720 --> 00:10:12,000

Create this New England resource, but first, let's make sure that everything has been set up according



102

00:10:12,000 --> 00:10:16,360

to the question, especially the back in parts, that looks correct.



103

00:10:16,380 --> 00:10:23,130

So let's now apply and create our new ingress resource and the critical space namespace.



104

00:10:24,490 --> 00:10:31,240

So let's run detailed and critical space, describe the new engross resource, and you can see that



105

00:10:31,240 --> 00:10:32,250

the part is correct.



106

00:10:32,260 --> 00:10:34,930

It's using the correct service and the correct port.



107

00:10:39,500 --> 00:10:46,550

So let's now try to access the service, I'd be appended to the end of the URL and looks like it's working



108

00:10:46,550 --> 00:10:47,470

as expected.



109

00:10:50,770 --> 00:10:57,660

And we have already seen the euro would be a benefit to the euro, and that's working well.



110

00:10:57,670 --> 00:10:59,230

So that's the last question.



111

00:11:00,160 --> 00:11:03,910

Thank you for joining me this video and I'll see you in the next one.