1
00:00:00,910 --> 00:00:02,560
Time to create our second workflow.

2
00:00:02,650 --> 00:00:06,540
So this one is going to be all about taking all those different config files inside of right in front,

3
00:00:06,610 --> 00:00:08,920
hey, it's directory and applying them to our cluster.

4
00:00:09,760 --> 00:00:12,580
This config files gonna look really similar to the one we just put together.

5
00:00:12,610 --> 00:00:15,460
In fact, it's even gonna be a little bit more straightforward.

6
00:00:15,720 --> 00:00:16,840
Well, let's get right to it.

7
00:00:17,730 --> 00:00:22,180
I'm going to first go and take a look at the deploy audio file that we just put together a moment ago.

8
00:00:22,880 --> 00:00:26,690
I'm going to copy all the stuff we had put inside there just to save myself a little bit of time.

9
00:00:27,140 --> 00:00:29,180
Like I said, it is going be very similar to this.

10
00:00:30,900 --> 00:00:36,770
I'll then go back to my workflows directory inside of here, I'm going to create a new file and I want

11
00:00:36,770 --> 00:00:39,830
to call it deploy dash manifests.

12
00:00:43,200 --> 00:00:46,370
All those config files are technically called manifest, by the way.

13
00:00:46,430 --> 00:00:48,200
So that's why we're calling it deploy manifests.

14
00:00:49,270 --> 00:00:51,700
And then going to a paste in everything that we just copied.

15
00:00:52,730 --> 00:00:55,170
Now we're going to make a couple of small changes inside of you.

16
00:00:55,780 --> 00:00:58,920
So first off, I cannot change the name to deploy manifests.

17
00:01:01,120 --> 00:01:04,700
I'm going to change paths to infra flash.

18
00:01:04,830 --> 00:01:05,490
Star, star.

19
00:01:08,260 --> 00:01:14,530
I'm then going to remove everything around building the image, logging into docker, pushing off to

20
00:01:14,530 --> 00:01:15,040
Docker.

21
00:01:15,520 --> 00:01:16,950
So those three steps right there.

22
00:01:17,060 --> 00:01:17,700
I delete them.

23
00:01:18,910 --> 00:01:21,360
So I should now only have a uses for dactyl.

24
00:01:21,980 --> 00:01:25,100
The doctor will step right here where we get that context.

25
00:01:25,760 --> 00:01:28,670
And then finally, where we are doing the rollout on the deployment.

26
00:01:28,880 --> 00:01:32,450
So in this case, we do not want to do any rollouts of deployment or anything like that.

27
00:01:32,720 --> 00:01:37,340
Instead, we want to apply all those config files we had placed into that Cades directory.

28
00:01:39,420 --> 00:01:45,760
Up inside of your QVC, T.L., apply Dasch F in front, slash K eights like so.

29
00:01:47,280 --> 00:01:49,170
And believe it or not, that should pretty much be it.

30
00:01:49,410 --> 00:01:51,930
So we're going to apply all those config files to our cluster.

31
00:01:55,430 --> 00:01:57,030
I'll then go down, commit to file.

32
00:01:57,990 --> 00:01:58,890
And that should be at.

33
00:02:00,750 --> 00:02:01,500
Now, as usual.

34
00:02:01,590 --> 00:02:02,750
No, that's not really it.

35
00:02:02,880 --> 00:02:05,670
It turns out there's one other thing that we need to be aware of.

36
00:02:06,450 --> 00:02:08,910
I want to give you a very quick reminder back inside of our editor.

37
00:02:08,970 --> 00:02:11,280
I cannot find my infra k its directory.

38
00:02:12,120 --> 00:02:13,860
Inside there is the Ingress service file.

39
00:02:14,450 --> 00:02:16,710
So we have put together this ingress configuration file.

40
00:02:16,770 --> 00:02:22,890
And we said that whenever a user goes to a host of ticketing dot dev, we want to apply this set of

41
00:02:22,890 --> 00:02:26,130
redirect rules and whatnot or routing rules to their request.

42
00:02:26,670 --> 00:02:29,490
The key thing here is that we have a host of ticketing dot def.

43
00:02:30,030 --> 00:02:32,910
Now we are about to deploy our application to the open Internet.

44
00:02:33,250 --> 00:02:37,530
And when we do so, we're going to eventually purchase a domain name and pointed at our application.

45
00:02:38,280 --> 00:02:42,720
When we do so, that domain name is probably going to be something different than ticketing dot dev.

46
00:02:42,780 --> 00:02:46,560
As a matter of fact, I can guarantee you it's going to be different because I'm going to end up with

47
00:02:46,560 --> 00:02:48,180
a different domain name than you are.

48
00:02:48,960 --> 00:02:54,780
So this little property right here at this very singular property really needs to be different, depending

49
00:02:54,780 --> 00:03:00,990
upon whether we are running our ingress service in our development cluster or on our production cluster.

50
00:03:01,950 --> 00:03:06,060
Right now, if we just take all these config files and apply them to our cluster, we will create a

51
00:03:06,060 --> 00:03:07,740
copy of Ingress and Genex.

52
00:03:07,830 --> 00:03:12,430
But unfortunately, it's always going to be looking for a user to come to ticketing dot dev.

53
00:03:13,020 --> 00:03:17,790
And if I go to ticketing dot dev on my local machine, it's always going to point to my local cluster,

54
00:03:18,210 --> 00:03:20,580
never, ever to the diploid cluster.

55
00:03:21,550 --> 00:03:23,840
So there are a couple of different ways we can solve this problem.

56
00:03:23,950 --> 00:03:27,320
We can take a quick pause right here and then figure out how to solve it in just a moment.