1
00:00:01,170 --> 00:00:04,340
We are just about ready to do a final test of our deployment process.

2
00:00:04,370 --> 00:00:09,290
But before we do one last little piece of setup, remember, before we make use of ingress, engine

3
00:00:09,320 --> 00:00:14,630
X inside of a cluster, we have to do a little set up command from the Ingress Engine X documentation.

4
00:00:15,260 --> 00:00:16,360
Let's go run that right now.

5
00:00:16,460 --> 00:00:20,030
We're going to execute that command manually against our digital ocean cluster.

6
00:00:20,710 --> 00:00:25,160
So inside of a new browser tab, I'm going to do a search for ingress, engine X.

7
00:00:26,460 --> 00:00:28,950
Going to find the home page for Ingress, Engine X right here.

8
00:00:30,280 --> 00:00:31,860
Well, then find the deployment section.

9
00:00:32,580 --> 00:00:36,990
And then remember, there are many different set commands depending upon how we are running our cluster.

10
00:00:37,590 --> 00:00:42,350
In our case, we are running our cluster on digital ocean language to go to the digital ocean setup

11
00:00:42,390 --> 00:00:42,840
command.

12
00:00:43,750 --> 00:00:44,410
Here it is right here.

13
00:00:45,540 --> 00:00:46,620
I will copy that command.

14
00:00:47,760 --> 00:00:49,510
And then going to go back over to my terminal.

15
00:00:49,960 --> 00:00:55,120
And before I run the command, I'm going to double check and make sure that my cube CTO client is connecting

16
00:00:55,120 --> 00:00:57,010
to my digital ocean cluster.

17
00:00:58,020 --> 00:01:01,670
Remember, you can verify that either by going to doctor for Windows or doctor for Mac.

18
00:01:01,920 --> 00:01:06,400
Taking a look at that Cuban menu dropdown and making sure that you're using your ticketing context.

19
00:01:07,260 --> 00:01:08,970
Alternatively, if you're using mini KUB.

20
00:01:10,120 --> 00:01:15,370
You're going to run those commands of cutesy T.L. config view that will tell you the name of your digital

21
00:01:15,370 --> 00:01:16,270
ocean context.

22
00:01:16,690 --> 00:01:21,490
You can take that name and then run QVC, DL config, use context and then that context name.

23
00:01:22,920 --> 00:01:25,770
So once you're a QVC, TLC instance is configured appropriately.

24
00:01:26,160 --> 00:01:28,350
Well, then pasted that command and run it.

25
00:01:31,370 --> 00:01:31,670
All right.

26
00:01:31,700 --> 00:01:33,960
Looks like everything is being created very good.

27
00:01:35,790 --> 00:01:39,630
So after all that stuff gets created, there is one last quick thing we have to do.

28
00:01:40,230 --> 00:01:41,490
We have made some changes.

29
00:01:42,440 --> 00:01:45,470
To the structure of our infra directory.

30
00:01:46,070 --> 00:01:49,070
So we've got all these changes to where all these different files live right now.

31
00:01:49,710 --> 00:01:53,960
So we need to make sure that we commit these changes and push them up to the master branch.

32
00:01:54,290 --> 00:01:56,480
So when we eventually merge our new code.

33
00:01:56,690 --> 00:02:01,550
Well, we'll pull along these changes with it and we will make sure that we only deploy the appropriate

34
00:02:01,580 --> 00:02:02,840
ingress service file.

35
00:02:03,990 --> 00:02:08,640
So we are going to commit these changes directly to master and push them up, not just, you know,

36
00:02:08,640 --> 00:02:10,470
when we commit to master and push them up.

37
00:02:10,920 --> 00:02:12,750
That is going to cause that works.

38
00:02:12,810 --> 00:02:17,010
That workflow that we just put together, the deployment workflow to run one time.

39
00:02:18,010 --> 00:02:22,720
So as soon as we push these changes up, specifically these split directories right here, that is going

40
00:02:22,720 --> 00:02:26,370
to cause a deployment to our digital ocean cluster.

41
00:02:27,180 --> 00:02:30,850
So we should Emili, after committing these and pushing them manually, we which build to inspect our

42
00:02:30,850 --> 00:02:33,880
cluster and see a bunch of deployments being created and stuff like that.

43
00:02:34,720 --> 00:02:36,160
Let's do that manually right now.

44
00:02:36,310 --> 00:02:41,170
And again, this is one the only times you're going to manually commit to master and push changes to

45
00:02:41,170 --> 00:02:41,620
master.

46
00:02:42,340 --> 00:02:46,150
In general, we are always going to open a pull request instead and use a portal quest to merge and

47
00:02:46,150 --> 00:02:46,750
changes.

48
00:02:48,500 --> 00:02:51,170
OK, so back in the terminal, I'm going to check out M..

49
00:02:52,840 --> 00:02:56,040
I gonna do a get status and just verify.

50
00:02:56,160 --> 00:02:57,980
Yep, I got those two directory changes.

51
00:02:58,220 --> 00:03:02,540
I got some changes to the Scaffold YAML file and I move the Ingress service file, two copies of it

52
00:03:02,540 --> 00:03:04,070
to those two new directories.

53
00:03:05,020 --> 00:03:06,350
Going to add all these changes.

54
00:03:08,010 --> 00:03:12,530
Going to commit them and I'll say split eights manifests.

55
00:03:14,120 --> 00:03:15,350
And then I will push to master.

56
00:03:20,140 --> 00:03:23,410
And I've got some changes up on master once again, my mistake.

57
00:03:23,800 --> 00:03:27,610
Once again, I need to do a poll or G.M. really quickly.

58
00:03:30,550 --> 00:03:35,950
After author, my merge message, and now I can do a push to Origin Master.

59
00:03:40,460 --> 00:03:41,240
All right, there we go.

60
00:03:41,960 --> 00:03:43,970
Now, if we go over to get Hub really quickly.

61
00:03:45,460 --> 00:03:47,710
And take a look at our actions tab.

62
00:03:47,830 --> 00:03:48,340
Once again.

63
00:03:50,570 --> 00:03:54,760
We're going to see if we click on it, deploy manifests and deploy off.

64
00:03:55,040 --> 00:03:58,520
We should see that there are some changes that have now been admitted.

65
00:03:58,550 --> 00:04:00,800
So we should see that split in four directory.

66
00:04:02,370 --> 00:04:04,420
And if we click on that and go to build.

67
00:04:05,790 --> 00:04:11,710
We should see that we successfully install Dactyl, that we apply to all girls olders inside of arcades

68
00:04:11,840 --> 00:04:16,170
and cades pro directories, and that everything was completed successfully.

69
00:04:17,600 --> 00:04:21,410
After we verify that everything was executed successfully, we should then be able to go back over to

70
00:04:21,410 --> 00:04:26,210
our terminal and then get a listing of all the pods running on our digital ocean cluster.

71
00:04:26,780 --> 00:04:29,360
We should be able to do a K or cube CTO.

72
00:04:29,960 --> 00:04:35,870
Get pods and that should run or get a list of all the pods that have been created on our cluster.

73
00:04:36,650 --> 00:04:41,120
Now, you'll notice that in my case, I've got some definite errors here, and that's solely OK.

74
00:04:41,390 --> 00:04:43,250
If you have errors, that is OK as well.

75
00:04:43,700 --> 00:04:47,750
We're going to first get all of our tooling put together and then we'll worry about doing some troubleshooting

76
00:04:47,750 --> 00:04:49,910
here and figuring out exactly what is going on.

77
00:04:51,070 --> 00:04:56,110
All we want to really see right now is that some resources were success or I shouldn't even say successfully

78
00:04:56,110 --> 00:04:56,530
created.

79
00:04:56,740 --> 00:05:00,430
We really just want to see that some pods are attempting to be created.

80
00:05:00,520 --> 00:05:01,960
That's all we want to see right now.

81
00:05:03,170 --> 00:05:09,530
All right, so now that I have verified that my get hub action workflow has tried to push some manifests

82
00:05:09,590 --> 00:05:10,460
off to my cluster.

83
00:05:10,820 --> 00:05:11,990
We're going to take a pause right here.

84
00:05:12,210 --> 00:05:13,430
We can come back the next video.

85
00:05:13,460 --> 00:05:18,680
We're going to test out making a pull request to our auth service and make sure that we can create a

86
00:05:18,890 --> 00:05:22,820
or up play request and see those changes get deployed to our cluster.

87
00:05:23,510 --> 00:05:27,620
Once we go through that workflow at least once, we're then going to do some troubleshooting and figuring

88
00:05:27,620 --> 00:05:30,620
out why some these different pods are failing to be created.