1 00:00:01,550 --> 00:00:05,210 It looks like my Cuban 80s cluster right here is still being created but there's a little bit of setup 2 00:00:05,240 --> 00:00:06,870 that we can do in the meantime. 3 00:00:07,100 --> 00:00:12,470 I want to give you a quick reminder that right now if we open up our terminal we can run cube TTL get 4 00:00:12,470 --> 00:00:18,430 pods and when we do so we're going to see some information about the cluster on our local machine. 5 00:00:18,470 --> 00:00:19,900 Now here's something interesting. 6 00:00:20,030 --> 00:00:24,070 How do we somehow connect to the cluster that we just created in Google Cloud. 7 00:00:24,080 --> 00:00:29,690 Well to access different clusters we're always going to end up using the same cubes EDL command behind 8 00:00:29,690 --> 00:00:34,940 the scenes there's some configuration options that are being applied to cube Seitel when we change those 9 00:00:34,940 --> 00:00:38,950 configuration options is going to change which cluster we are connecting to. 10 00:00:38,960 --> 00:00:41,730 Let me show you a diagram just help you understand. 11 00:00:41,850 --> 00:00:42,230 All right. 12 00:00:42,260 --> 00:00:48,040 So quick diagram right here so on our local machine we are currently running cube Seitel behind the 13 00:00:48,040 --> 00:00:53,560 scenes cube Seitel uses something called context context can be thought of essentially as some different 14 00:00:53,560 --> 00:01:00,760 connection settings they list out some authorization credentials some users some IP addresses a lot 15 00:01:00,760 --> 00:01:05,860 of different information to tell cube Seitel how to connect that to different clusters that exist in 16 00:01:05,860 --> 00:01:12,430 the world right now we are connecting to our local cluster through a context was created when we first 17 00:01:12,430 --> 00:01:16,020 installed Docker for Windows or Docker from Mac on your machine. 18 00:01:16,270 --> 00:01:20,920 As a matter of fact if you go to your Docker icon right now and then mouse over Cuban eddies you'll 19 00:01:20,920 --> 00:01:27,860 see something it says context right there in our current context is Docker dash desktop so this context 20 00:01:27,860 --> 00:01:32,900 right here has some connection settings inside of it to tell us how to connect to our local cluster 21 00:01:33,800 --> 00:01:39,410 we need to add in a second context a new context that's going to tell cube Seitel how to connect to 22 00:01:39,410 --> 00:01:45,140 the cluster that we just created in Google Cloud there's two ways we can do this we can either use the 23 00:01:45,170 --> 00:01:51,530 Google cloud dashboard over here and go through a series of different menus to find some little config 24 00:01:51,530 --> 00:01:57,350 that we would copy paste into a file on our local machine that would be one way to add the context another 25 00:01:57,350 --> 00:02:04,550 way that is a lot easier is to instead install a tool called the Google cloud SDK this is a command 26 00:02:04,550 --> 00:02:10,430 line tool that we can use to interface with Google Cloud automatically the Google cloud SDK does a ton 27 00:02:10,460 --> 00:02:15,680 of different things but one thing that it does for us is create these different contexts for us automatically 28 00:02:16,190 --> 00:02:21,470 and update cubes GTL on our look machine and teach it how to connect to the clusters that we are creating 29 00:02:21,500 --> 00:02:27,490 in Google Cloud so we are now going to install this Google Cloud SDK and it's going to automatically 30 00:02:27,490 --> 00:02:33,700 manage these context things for us to install the Google cloud SDK we're gonna go to the address you 31 00:02:33,700 --> 00:02:37,950 see right here on the screen now these URLs of course break every now and then. 32 00:02:37,960 --> 00:02:42,160 So if you try to go to that to this address and it doesn't work well you have to do is do a quick google 33 00:02:42,160 --> 00:02:48,180 search for Google Cloud SDK and you'll see a link come up for it right away it's going to take that 34 00:02:48,180 --> 00:02:54,390 your URL and visit it inside of a new tab will then be prompted here with installation directions for 35 00:02:54,390 --> 00:02:56,360 a variety of different operating systems. 36 00:02:56,490 --> 00:02:57,530 So as you'd guess. 37 00:02:57,570 --> 00:03:03,780 Just go ahead and select your appropriate operating system and it will show you some installation directions. 38 00:03:03,780 --> 00:03:10,130 Now in every case there's going to be kind of a series of different installation parts in here. 39 00:03:10,230 --> 00:03:12,820 So you'll see a one that says something like before you begin. 40 00:03:13,050 --> 00:03:18,330 Those will be some steps to do initially and then eventually it'll have something about initialize the 41 00:03:18,330 --> 00:03:19,530 SDK. 42 00:03:19,530 --> 00:03:21,810 You do not have to initialize the SDK just yet. 43 00:03:21,810 --> 00:03:24,570 You and I are going to do that together in the next video. 44 00:03:24,630 --> 00:03:30,000 So all you have to do is go through the process of installing the SDK and then going through any additional 45 00:03:30,000 --> 00:03:35,850 steps that it recommends such as this optional one right here to get access to the cloud SDK very easily 46 00:03:35,850 --> 00:03:36,930 through your terminal. 47 00:03:37,170 --> 00:03:40,240 Again you do not want to run the cloud in command. 48 00:03:40,290 --> 00:03:43,150 We're going to do that together in just a moment. 49 00:03:43,250 --> 00:03:43,480 All right. 50 00:03:43,490 --> 00:03:45,230 So go ahead and install this thing. 51 00:03:45,230 --> 00:03:48,590 We'll come back the next video and we'll go to it initialization process together.