1

00:00:00,420 --> 00:00:07,080

This is the solution video for the Saeki, a mock exam one, so for the first question, we have to



2

00:00:07,080 --> 00:00:11,910

deploy a bot named engine expert using the Ingenix out by an image.



3

00:00:15,720 --> 00:00:20,490

To do this, we will use the imperative come on, Cuba, we'll run.



4

00:00:22,520 --> 00:00:25,100

The name of the port is in the next part.



5

00:00:26,120 --> 00:00:28,700

And the image is Ingenix Alpine.



6

00:00:31,000 --> 00:00:34,540

So this should create a pot by that name and image.



7

00:00:38,450 --> 00:00:44,150

That's verify using capacity, get pots can see that it's in a container creating said.



8

00:00:46,260 --> 00:00:50,180

Now it's now running state, so let's move on to the next question.



9

00:00:51,920 --> 00:00:58,880

Deploy our messaging pod using the latest Alpine image with the labels set to cheer as a call to message.



10

00:01:03,800 --> 00:01:05,990

So we'll use the same comment as before.



11

00:01:06,750 --> 00:01:08,600

Let's copy the label.



12

00:01:09,610 --> 00:01:12,070

And we'll use the same command, Cukier.



13

00:01:13,630 --> 00:01:14,040

Run.



14

00:01:14,890 --> 00:01:17,770

And let's change the name of the party to messaging.



15

00:01:20,800 --> 00:01:23,110

The inmates should be released, Alpine.



16

00:01:25,380 --> 00:01:33,660

And we'll use the dash el option and paste the label, which is a key value pair here as a message.



17

00:01:35,640 --> 00:01:37,290

So now that part has been created.



18

00:01:38,800 --> 00:01:43,180

We can validate by running Kubasik, we'll get parts that are shoe labels.



19

00:01:44,690 --> 00:01:48,200

And we see that messaging has called decreased global.



20

00:01:50,840 --> 00:01:57,550

Next year, to create a namespace by the name of Apex Dash X nine nine eight four five seven four,



21

00:01:57,560 --> 00:02:04,280

so let's copy the name of the namespace and we'll use the command cube to create an S, which is short



22

00:02:04,280 --> 00:02:09,420

for namespace and P is the name that has created the namespace.



23

00:02:09,440 --> 00:02:11,610

So yeah, let's move on to the next question.



24

00:02:12,590 --> 00:02:19,430

So for this, we have to get the output of all the notes of the cluster in adjacent format and redirect



25

00:02:19,430 --> 00:02:20,270

to a file.



26

00:02:22,590 --> 00:02:27,000

So to do this, we will run Cuba, we'll get notes.



27

00:02:28,410 --> 00:02:32,910

And we'll get that enough format of Jaeson using the dash or.



28

00:02:33,850 --> 00:02:34,510

Jason.



29

00:02:35,390 --> 00:02:35,840

Come on.



30

00:02:36,110 --> 00:02:39,870

So first, let's try and get we see that there are two notes.



31

00:02:39,890 --> 00:02:45,640

So now let's use Dasch or Jason, which gives us all the details and a decent format.



32

00:02:45,650 --> 00:02:47,750

And now let's redirected to the file.



33

00:02:49,880 --> 00:02:50,520

That should be it.



34

00:02:50,540 --> 00:02:52,790

Let's move on to the next question.



35

00:02:54,290 --> 00:03:00,800

Create a service called Messaging Service to expose the messaging application within the cluster on



36

00:03:00,800 --> 00:03:02,210

board six three seven nine.



37

00:03:02,870 --> 00:03:10,070

So now we have to create a new service for the part that we created earlier called messaging, and it



38

00:03:10,070 --> 00:03:14,170

should be exposed within the cluster on board return.



39

00:03:14,270 --> 00:03:18,290

So for this, let's use the command cubicle expose.



40

00:03:19,260 --> 00:03:19,770

Part.



41

00:03:21,050 --> 00:03:26,900

The name of the pod, which is messaging the name of the service as messaging service and a space that



42

00:03:26,900 --> 00:03:31,070

here and let's use that dashboard as equal to six three seven nine.



43

00:03:32,720 --> 00:03:35,930

We also have to provide the target board, which is six three seven nine.



44

00:03:39,160 --> 00:03:40,610

And that should be it.



45

00:03:40,870 --> 00:03:45,440

So if you're on this command, it should automatically create the service for the great selectors.



46

00:03:45,460 --> 00:03:48,190

So let's use Kube still describe as we see.



47

00:03:48,830 --> 00:03:53,400

And here you can see that it is using the port 67 nine.



48

00:03:53,410 --> 00:03:59,260

It has got one end point and it does using the correct selector of TerraCycle message.



49

00:03:59,830 --> 00:04:02,890

And it has created a cluster type type service.



50

00:04:04,140 --> 00:04:12,090

So let's move on, create a deployment named H.R. Dasch Web app using the image called cloud web app



51

00:04:12,090 --> 00:04:13,560

color with two replicas.



52

00:04:16,030 --> 00:04:18,670

So let's copy the name of the image from the question.



53

00:04:20,500 --> 00:04:25,270

And we'll make use of the command cube to create deployment.



54

00:04:26,290 --> 00:04:32,110

The name is H.R. Dasch Web app, the image name, let's be Sudheer.



55

00:04:33,630 --> 00:04:38,220

And to scale it to two replicas will use still scale deployment.



56

00:04:39,180 --> 00:04:42,090

The name of the deployment dashers replicas is equal due to.



57

00:04:47,580 --> 00:04:52,410

To validate Lindstrand capacity, you'll get deployment's, and here you can see that it two of two



58

00:04:52,410 --> 00:04:53,580

pots ready.



59

00:04:57,730 --> 00:05:04,450

Next year to create a static board named Static Dash busy box on the Mustonen that uses the busy box



60

00:05:04,450 --> 00:05:07,540

image and the command sleep one thousand.



61

00:05:09,280 --> 00:05:16,000

So this should be a strategy box, so we'll have to create a configuration file and place it in the



62

00:05:16,840 --> 00:05:18,850

pot use by Satake Pots.



63

00:05:20,030 --> 00:05:25,170

So let's generate the configuration file for the part first, so we're making use of your run.



64

00:05:25,250 --> 00:05:27,200

Let's name it to static.



65

00:05:28,560 --> 00:05:34,900

The Xbox, the image, let's change it to the Xbox, let's move the label.



66

00:05:40,760 --> 00:05:43,280

And let's at the command, which is.



67

00:05:45,530 --> 00:05:47,090

Sleep one thousand.



68

00:05:52,100 --> 00:05:58,520

And let's use the dry run feature here, created another in Yemen format and redirected to a file called



69

00:05:58,520 --> 00:06:00,110

Static Dash Xbox.



70

00:06:00,650 --> 00:06:04,190

So right now it is creating it and the root directory will.



71

00:06:05,170 --> 00:06:10,300

Update the configuration file if needed, but it looks like everything is.



72

00:06:11,140 --> 00:06:15,430

As it should be, so let's determine the directory where the.



73

00:06:16,390 --> 00:06:23,450

Such reports are created by default for Cuba, Adam created clusters, it was created under the D.C.



74

00:06:23,560 --> 00:06:25,770

Cabinet as manifest directory.



75

00:06:28,090 --> 00:06:33,880

So here we have four files for the four static parts for our controlling components, so this is where



76

00:06:33,880 --> 00:06:37,800

we should be adding that in part to validate let's check the Kubelik configuration.



77

00:06:38,320 --> 00:06:47,510

So here, let's go to see this wall Kubelik and graph for the string static part within the conflict



78

00:06:47,510 --> 00:06:48,080

document.



79

00:06:48,340 --> 00:06:55,750

And here you can see that the static part part is set to discriminators manifest actory as expected.



80

00:06:58,440 --> 00:07:06,150

So now we will just move the file that we created in the root directory called Starting with the Box,



81

00:07:06,150 --> 00:07:11,300

and we'll move it to the appropriate directory, which is it is when it is manifest.



82

00:07:11,730 --> 00:07:14,130

And now if you're on CubeSat, you'll get Pottz.



83

00:07:14,130 --> 00:07:18,540

You should see that allostatic part by the name of starting the Xbox.



84

00:07:18,540 --> 00:07:20,100

Masser has been created.



85

00:07:24,240 --> 00:07:31,170

Now create a board in the finance namespace named Damp Bus with the image is Alpine.



86

00:07:32,390 --> 00:07:35,630

So we have to create a part in a different namespace.



87

00:07:36,140 --> 00:07:40,940

So first let's check of the names with exists so we don't get in.



88

00:07:40,940 --> 00:07:44,510

As I can see that the finance needs to be a success.



89

00:07:45,260 --> 00:07:49,640

So, again, let's make use of the same as before, which is still run.



90

00:07:54,770 --> 00:08:01,460

So let's make sure that we have the correct options for the comments being used, so the name should



91

00:08:01,460 --> 00:08:05,330

be tempered by bus and it should use its Alpine.



92

00:08:08,640 --> 00:08:10,950

So let's seize the image name first.



93

00:08:14,270 --> 00:08:16,070

And then the name of the pod.



94

00:08:22,230 --> 00:08:26,910

OK, so now we are redirecting the configuration to allow you to move to.



95

00:08:28,610 --> 00:08:29,810

Call Baudot YAML.



96

00:08:35,170 --> 00:08:40,440

You know, we can also try to add the name space feel within the come on and let's see if that works.



97

00:08:41,630 --> 00:08:46,320

So looks like that did not take, but that's OK, we can add the value within the file.



98

00:08:46,700 --> 00:08:53,420

So here I am in the editor, so I'm just going to add the namespace is equal to finance under the metadata



99

00:08:53,420 --> 00:08:53,900

section.



100

00:08:54,970 --> 00:09:00,730

The rest of the fields look correct, so let's create this pot.



101

00:09:04,550 --> 00:09:10,490

What has been created, let's verify by checking it and the finance ministry and you can see that it



102

00:09:10,490 --> 00:09:11,390

is running.



103

00:09:13,810 --> 00:09:17,100

We want a new application called Orange is Deployed.



104

00:09:17,110 --> 00:09:19,960

There's something wrong with it, identify and fix the issue.



105

00:09:21,390 --> 00:09:25,910

So first, let's check if a deployment or a part has been created by the name of Orange.



106

00:09:25,960 --> 00:09:27,470

So first, let's check deployments.



107

00:09:28,050 --> 00:09:29,760

So it looks like it's not created.



108

00:09:29,790 --> 00:09:30,810

Let's check what's.



109

00:09:32,790 --> 00:09:38,880

And you can see that there is a report by the name of Orange, and if you see the cities, you can see



110

00:09:39,540 --> 00:09:41,840

that it is in a crash to back off.



111

00:09:41,850 --> 00:09:46,670

And you can also see that it has gotten in a container, which is in a crash back of it.



112

00:09:46,680 --> 00:09:48,570

So let's describe the part.



113

00:09:49,970 --> 00:09:52,190

And scroll up and see the status.



114

00:09:54,310 --> 00:09:58,610

So they should have two containers, one should be in any container and one should be regular.



115

00:09:58,630 --> 00:10:04,690

So this is the regular container by the name of orange container, which is innervating, said the most



116

00:10:04,690 --> 00:10:07,420

likely it's waiting for the container to complete.



117

00:10:07,720 --> 00:10:08,200

So.



118

00:10:09,420 --> 00:10:17,340

Let's crawl up and here is the container called a net dash my service, and that is innervating state



119

00:10:17,340 --> 00:10:18,950

and the last state was terminated.



120

00:10:18,960 --> 00:10:24,830

And if you see the command that it's using is incorrect, there's a typo for the come on sleep.



121

00:10:24,840 --> 00:10:26,250

So, yeah, let's fix that.



122

00:10:27,730 --> 00:10:37,360

And as a result, that's the reason why the parties in arrows said, so let's get the configuration



123

00:10:37,360 --> 00:10:45,850

and the Yamal format for the part, then will delete the existing part, wait for the part to terminate



124

00:10:45,850 --> 00:10:50,620

completely, and then we will edit the configuration file that we just generated.



125

00:10:53,640 --> 00:11:02,540

So let's go down to the container section and look up the come on sleep, which is incorrect here.



126

00:11:02,660 --> 00:11:04,770

Let's correct it and save the file.



127

00:11:05,280 --> 00:11:09,330

Now, if we create the part, it should work.



128

00:11:09,900 --> 00:11:12,390

So, again, let's check the status.



129

00:11:13,640 --> 00:11:19,680

And you can see that the container is running those initializing and now it's now running straight.



130

00:11:19,700 --> 00:11:25,270

So that means that the container was successful and the second regular container is now running as well.



131

00:11:27,110 --> 00:11:34,330

So for the next question, expose the HRR Web app as a service, the name of the service at our Web



132

00:11:34,370 --> 00:11:38,420

Dash Abda service, it should be exposed on both.



133

00:11:39,410 --> 00:11:44,480

Three hundred eighty two on the nose of the Colossus on this case, we have to create a new inaudible



134

00:11:44,510 --> 00:11:45,500

type service.



135

00:11:47,840 --> 00:11:55,220

So we have already created that the deployment, which is at our Web dash app.



136

00:11:59,460 --> 00:12:04,860

So to do this, Let's Run explores deployment, the name of the deployment.



137

00:12:05,910 --> 00:12:07,530

And the name of the service.



138

00:12:08,760 --> 00:12:12,750

And we'll make use of dash dash type, the call to not put.



139

00:12:14,240 --> 00:12:16,910

And let's make use of the port, which is.



140

00:12:18,070 --> 00:12:21,430

Eight zero eight zero and the target put as AIDS rates were as well.



141

00:12:22,630 --> 00:12:25,330

So, again, we'll make use of the dash dash dry run.



142

00:12:27,260 --> 00:12:36,440

There is currently no way to specify the name of the norpoth or specify the note put two three zero



143

00:12:36,440 --> 00:12:37,160

zero eight two.



144

00:12:37,700 --> 00:12:41,210

So we'll generate a configuration file.



145

00:12:42,310 --> 00:12:47,260

And redirected to escort YAML, let's manually update the node port.



146

00:12:51,570 --> 00:12:53,250

Two three zero zero eight two.



147

00:12:56,670 --> 00:13:00,990

And that should be it, so we can now save this file and create the service.



148

00:13:08,100 --> 00:13:15,360

To validate, let's try and describe, as we see in the name of the service and here we can see that



149

00:13:15,360 --> 00:13:22,410

it has got to end points and it is using the norpoth type, which is said to translate to.



150

00:13:24,030 --> 00:13:31,050

So for this next question, we have to make use of decent battery to retrieve the EU's images of all



151

00:13:31,050 --> 00:13:32,860

the notes and store it and have fun.



152

00:13:33,750 --> 00:13:40,860

And there is also a hint that the US images field is under the north info section under the status of



153

00:13:40,860 --> 00:13:41,510

each port.



154

00:13:44,560 --> 00:13:47,680

So in this case, we'll make use of these and Pat.



155

00:13:49,910 --> 00:13:53,330

And we'll also make use of the documentation.



156

00:13:54,770 --> 00:13:58,460

To help us get the correct come on.



157

00:14:00,650 --> 00:14:05,360

So now let's go to the corner of documentation and search for Jason.



158

00:14:08,480 --> 00:14:14,360

And here you'll find that there is a document called Cupidity Your Cheat Sheet, which is really handy



159

00:14:14,360 --> 00:14:19,940

and has a lot of examples for all the cube still commands.



160

00:14:20,480 --> 00:14:26,810

And if you scroll down, you'll see a lot of examples related to this in part as well, which can be



161

00:14:26,810 --> 00:14:30,860

pretty handy to make use of during the exam.



162

00:14:31,340 --> 00:14:34,280

So in this case, it's specifically looking for capsid.



163

00:14:34,310 --> 00:14:37,230

You'll get notes and there is an example which is perfect for this use case.



164

00:14:37,250 --> 00:14:44,630

So, yeah, let's copy it and try to list the node configuration using this in.



165

00:14:44,980 --> 00:14:49,300

In this case, we have to make use of the flag, which is mezger.



166

00:14:49,310 --> 00:14:50,300

So let's add that.



167

00:14:50,810 --> 00:14:56,120

And in this case, we are trying to list all the items within the node configuration.



168

00:14:56,130 --> 00:14:57,980

So that'll pull out a lot of information.



169

00:14:57,980 --> 00:14:58,930

That's not what we need.



170

00:14:59,420 --> 00:15:01,010

So we'll have to drill down even further.



171

00:15:01,010 --> 00:15:06,530

And from the question we saw that it should be under the status section.



172

00:15:07,510 --> 00:15:09,380

So, yeah, let's drill down even further.



173

00:15:09,420 --> 00:15:11,980

So should be under status dot info.



174

00:15:12,860 --> 00:15:18,290

And you can see that it has filtered the output a little bit, but again, we are looking for B with



175

00:15:18,290 --> 00:15:18,540

the image.



176

00:15:18,570 --> 00:15:23,010

So if you're not really sure, we can still get no or Jason.



177

00:15:23,450 --> 00:15:31,640

And here I'm using a picture of less and we can see the entire Jaeson output this way and we can look



178

00:15:31,640 --> 00:15:34,370

at the section that we really need to drill down.



179

00:15:34,820 --> 00:15:39,760

So in this case, we know that the north info is under the status section.



180

00:15:39,770 --> 00:15:43,350

So you just scroll down or you can also make use of such.



181

00:15:43,350 --> 00:15:50,480

You'd at least like grep or search within the text editor itself for the feel that you're looking for



182

00:15:50,480 --> 00:15:52,790

and try to create the command.



183

00:15:52,820 --> 00:15:53,990

So this is optional.



184

00:15:53,990 --> 00:16:00,050

But, yeah, something which can be handy if you do not know which section to pass through and which



185

00:16:00,050 --> 00:16:01,430

command to use.



186

00:16:02,630 --> 00:16:08,570

So in this case, against that, there is an order and protection under the status and within that we



187

00:16:08,570 --> 00:16:15,020

have a map with image which provides V with image for all the notes of this cluster.



188

00:16:17,130 --> 00:16:19,620

So, yeah, let's go back and update our come on.



189

00:16:21,470 --> 00:16:24,860

So, yeah, let's add in with image.



190

00:16:27,370 --> 00:16:33,580

And this should narrow down and print out only the EU's images for the notes, so that looks like the



191

00:16:33,580 --> 00:16:34,350

correct options.



192

00:16:34,360 --> 00:16:38,350

And now let's read directly to the file, which was asked and the question.



193

00:16:42,000 --> 00:16:43,380

And that should be it.



194

00:16:43,680 --> 00:16:46,310

So let's move on to the final question.



195

00:16:49,100 --> 00:16:53,630

So we had to create a volume and the spec is provided on the right.



196

00:16:54,570 --> 00:16:57,660

So for this, again, we'll make use of the equipment and his documentation.



197

00:16:57,690 --> 00:17:02,850

There are no imperative commands as of now which we can use to create a persistent volume.



198

00:17:02,850 --> 00:17:05,430

So we'll use an example from the documentation.



199

00:17:07,780 --> 00:17:10,330

So in this case, it is making use of a hotspot.



200

00:17:13,350 --> 00:17:16,030

So all we need is the template to be used.



201

00:17:16,230 --> 00:17:17,370

So let's scroll down.



202

00:17:18,360 --> 00:17:20,790

I'm just searching for a spot here.



203

00:17:21,810 --> 00:17:25,290

And see if there is an exact example that we can use.



204

00:17:26,370 --> 00:17:32,930

And in this case, we don't see example of persistent volume, which makes use of hotspot directly,



205

00:17:33,000 --> 00:17:38,010

but that's OK, we can make use of our template and add the required field.



206

00:17:41,970 --> 00:17:48,180

So in this case, doesn't look like there is an exact example that we can copy, but yeah, let's just



207

00:17:48,180 --> 00:17:49,170

copy the template.



208

00:17:50,760 --> 00:17:52,050

Of opposites in volume.



209

00:17:55,220 --> 00:17:57,380

And so we'll make use of this template here.



210

00:18:00,240 --> 00:18:01,110

So, Kopi.



211

00:18:02,640 --> 00:18:03,660

Some of the lines.



212

00:18:05,210 --> 00:18:07,940

And we'll update it and according to our question.



213

00:18:08,980 --> 00:18:12,070

So I'm going to create a file called Dot Yamal.



214

00:18:16,930 --> 00:18:21,490

And the name of the process and volume should be read and latex.



215

00:18:25,160 --> 00:18:27,290

Let's go back to the documentation.



216

00:18:28,170 --> 00:18:30,920

And copy this back section as well.



217

00:18:36,670 --> 00:18:38,360

So let's update the mood.



218

00:18:38,440 --> 00:18:39,910

It should be retried many.



219

00:18:45,720 --> 00:18:51,530

We do not need the volume also, I'll delete that and let's update the size of the posts volume as well



220

00:18:51,540 --> 00:18:53,100

in accordance to the question.



221

00:18:55,120 --> 00:18:57,190

And the last thing that we want to add is the whole.



222

00:18:57,510 --> 00:19:00,010

So that's not something which is in the documentation.



223

00:19:01,650 --> 00:19:07,310

At least not a direct example that we can use, but in this case, it looks like they are using Neff's



224

00:19:07,320 --> 00:19:10,590

material just seems like the worst part and U.S. option.



225

00:19:21,280 --> 00:19:27,220

So one other comment that I find handy is Kubasik, you'll explain, and the object and make use of



226

00:19:27,220 --> 00:19:28,480

the dash recursive.



227

00:19:29,170 --> 00:19:36,370

So here I'm using less and within that I'll search for Hotspot just to see the different options that



228

00:19:36,370 --> 00:19:38,530

has to be used with this field.



229

00:19:39,070 --> 00:19:42,430

So you can see that the hotspot has an object.



230

00:19:44,400 --> 00:19:47,020

And that the object name is.



231

00:19:47,330 --> 00:19:52,380

So that's something that we have to add in and that should be under the spec section, so let's make



232

00:19:52,380 --> 00:19:54,710

sure that it is intended correctly.



233

00:19:57,060 --> 00:20:01,980

And within that, as we saw in the cubicle explain command, there should be a part feel that we have



234

00:20:01,980 --> 00:20:06,410

to enter and this is the whole spot which we have copied from the question.



235

00:20:07,350 --> 00:20:08,140

So that should be heard.



236

00:20:08,160 --> 00:20:12,150

Let's now create the processing volume using capacity or create.



237

00:20:14,340 --> 00:20:20,100

And you can see that deposition volume has been inspected by running CubeSat, you'll get Peevey, which



238

00:20:20,100 --> 00:20:21,470

is short for position volume.



239

00:20:21,990 --> 00:20:26,280

And here you can see that deposition volume with the correct options has been created.



240

00:20:26,290 --> 00:20:28,480

The access straight right?



241

00:20:28,500 --> 00:20:32,460

Many the signs is great and the current status is available.



242

00:20:32,470 --> 00:20:34,250

So that should be it.



243

00:20:35,040 --> 00:20:39,560

We can also run capacity of the strike to make sure that the it is using the correct spot.



244

00:20:39,580 --> 00:20:42,390

So here it is using the bodies.



245

00:20:42,390 --> 00:20:43,470

But the question.



246

00:20:44,470 --> 00:20:49,570

So now let's end the exam and run the evaluation just to make sure that we've got everything correct.



247

00:20:58,780 --> 00:21:05,560

So in case you got any of the answers wrong, you can go back to the Domhnall and fix it and run the



248

00:21:05,560 --> 00:21:06,420

evaluation again.



249

00:21:06,430 --> 00:21:11,400

So don't worry if you get anything wrong in the beginning, but that's the end of the solution.



250

00:21:11,410 --> 00:21:11,730

We do.



251

00:21:11,740 --> 00:21:14,440

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