1 00:00:01,380 --> 00:00:03,640 We've now installed an initialized doctor. 2 00:00:04,030 --> 00:00:08,740 Now we're going to use octal with a series of different commands to load up some contacts to connect 3 00:00:08,740 --> 00:00:10,330 to that new cluster that we just created. 4 00:00:11,330 --> 00:00:16,330 The first thing to do is install some context onto our local machine about that new cluster. 5 00:00:16,930 --> 00:00:18,650 So this is the command we're going to run right here. 6 00:00:18,670 --> 00:00:24,490 Dactyl Community is cluster Q config save and then the name of your cluster to get the name of your 7 00:00:24,490 --> 00:00:24,880 cluster. 8 00:00:24,910 --> 00:00:29,930 You can go back to the Cuban Nettie's dashboard book on Cuba, Nettie's left hand side, and it's going 9 00:00:29,930 --> 00:00:31,630 to be at whatever is listed right there. 10 00:00:31,840 --> 00:00:33,460 So in my case, all these simply ticketing. 11 00:00:35,410 --> 00:00:37,690 So I got to run that command right there. 12 00:00:38,840 --> 00:00:39,830 Back at my terminal. 13 00:00:41,230 --> 00:00:43,850 And I'm going to replace that Kluster name with ticketing. 14 00:00:46,610 --> 00:00:50,800 Once I run that command, I'll be told that some credentials have been added to my cube config file, 15 00:00:50,840 --> 00:00:52,910 which is where all of our different context gets saved. 16 00:00:53,600 --> 00:00:56,690 And then it automatically sets my context to my cluster. 17 00:00:57,230 --> 00:01:02,360 So if I now issue any commands against Cubes, DTL, they will be ran against the cluster that is running 18 00:01:02,360 --> 00:01:03,180 on dissolution. 19 00:01:04,010 --> 00:01:05,370 For example, I can do a cube ZT. 20 00:01:05,380 --> 00:01:06,200 I'll get pods. 21 00:01:07,380 --> 00:01:12,010 And I'll see that absolutely nothing is running, even if I am running some pods right now on my local 22 00:01:12,040 --> 00:01:14,320 machine or on my local communities, Kluster. 23 00:01:15,600 --> 00:01:19,920 I can also feel that more proof here would be a get node's and that will list out all the different 24 00:01:19,920 --> 00:01:20,910 nodes that are connected. 25 00:01:21,460 --> 00:01:24,630 So I've got three nodes right now that are connected to my digital ocean cluster. 26 00:01:24,870 --> 00:01:27,990 And naturally on my local machine, I only have one at most. 27 00:01:29,480 --> 00:01:34,640 Now, of course, at some point time, we will want to swap back to our local machine context, or perhaps 28 00:01:34,670 --> 00:01:39,320 if you're running everything on Google Cloud, as I showed you earlier on inside the course, you might 29 00:01:39,320 --> 00:01:41,750 be or want to talk back over to that context. 30 00:01:43,110 --> 00:01:47,810 So to do so, you can list out all the different contacts you have access to with QVC, T.L. config 31 00:01:47,930 --> 00:01:48,320 view. 32 00:01:49,540 --> 00:01:50,420 So we'll do that right now. 33 00:01:53,800 --> 00:01:56,140 And that's got to list out a lot of connection information. 34 00:01:56,740 --> 00:02:02,110 Well, we are really looking for here is a section called Context, but here it is right here, contexts. 35 00:02:02,740 --> 00:02:04,660 And then there are a couple of options. 36 00:02:04,690 --> 00:02:05,920 And each of them have a name. 37 00:02:06,520 --> 00:02:08,170 That name is what we care about. 38 00:02:08,580 --> 00:02:15,160 So to connect to my digital ocean cluster, that is the name or the context that I want to use if I 39 00:02:15,160 --> 00:02:20,170 want to swap back to using my local communities cluster that are running on my machine. 40 00:02:20,440 --> 00:02:25,390 I can either use a cluster or a contact name of Docker desktop or Docker for desktop. 41 00:02:25,510 --> 00:02:26,320 Either one is fine. 42 00:02:27,360 --> 00:02:32,980 So if I want to swap back to my local cluster, I'll do a QVC, T.L. config, use context and then the 43 00:02:32,980 --> 00:02:35,260 name of cubes T.L.. 44 00:02:36,450 --> 00:02:37,470 Was it config? 45 00:02:38,750 --> 00:02:41,600 Use context and then the name of Dr Desktop. 46 00:02:42,590 --> 00:02:45,230 If I now do a QCT, I'll get node's. 47 00:02:45,510 --> 00:02:46,680 I'll see just one note. 48 00:02:46,980 --> 00:02:48,180 My doctor desktop node. 49 00:02:49,190 --> 00:02:54,020 As a good reminder, if you are using debt doctor desktop, as opposed to using Docker tool box or something 50 00:02:54,020 --> 00:02:59,060 like that, you can always go to that tray icon and select your contacts from right here as well. 51 00:02:59,210 --> 00:02:59,930 A little bit easier. 52 00:03:00,350 --> 00:03:02,900 I just want to show you the kind of behind the scenes way of doing this stuff. 53 00:03:04,230 --> 00:03:06,220 I can swap back over to my digital ocean. 54 00:03:08,230 --> 00:03:10,450 Do another get pods once again, no pods. 55 00:03:10,480 --> 00:03:12,390 Because I'm not running anything on there just yet. 56 00:03:13,350 --> 00:03:13,510 OK. 57 00:03:13,580 --> 00:03:19,140 So, again, we are not going to deploy anything directly to our cluster by connecting to it and then 58 00:03:19,170 --> 00:03:22,950 applying anything, we're always going to rely upon our get hub workflow. 59 00:03:23,460 --> 00:03:28,080 The only reason I'm showing you how to connect directly to the cluster is that you can do some debugging, 60 00:03:28,560 --> 00:03:34,320 tried to pull logs, stuff like that, so that we understand how to connect that cluster manually. 61 00:03:34,620 --> 00:03:40,410 We're going to repeat a pretty similar process by creating a new GitHub workflow where we're going to 62 00:03:40,410 --> 00:03:43,860 connect to that cluster that we just created by using dactyl. 63 00:03:44,400 --> 00:03:49,320 We're then going to make sure that after we merge a pull request, we then attempt to apply all of our 64 00:03:49,320 --> 00:03:52,260 different config files for communities, all that kind of stuff. 65 00:03:53,130 --> 00:03:56,460 So quick pause and let's get started on that process in just a moment.