1 00:00:00,790 --> 00:00:05,080 Now that the Google cloud SDK is all installed and configured we're going to tell it to go and fetch 2 00:00:05,080 --> 00:00:09,630 some context information to connect to the cluster we just created in Google cloud. 3 00:00:09,730 --> 00:00:14,480 Now how we do this really comes down to a little decision that you need to make on your end. 4 00:00:14,740 --> 00:00:19,410 At this point time we still have Docker for Mac or Docker for Windows running up here. 5 00:00:19,410 --> 00:00:24,330 So if I click on that little icon Yep Docker is running and Cuban 80s is running. 6 00:00:24,430 --> 00:00:29,710 If you do not want to run Docker on your local machine at all anymore then you're going to run the two 7 00:00:29,710 --> 00:00:32,710 commands you see over here to the left hand side. 8 00:00:32,710 --> 00:00:38,080 First off you're going to close Docker desktop so you'll go up there and hit quit Docker desktop. 9 00:00:38,080 --> 00:00:44,830 You'll then run Google Cloud or G Cloud components install cube CTO that will grab a custom version 10 00:00:44,890 --> 00:00:52,100 or really not a custom version but it will grab cube Seitel and install it on your local machine because 11 00:00:52,100 --> 00:00:57,080 of that you no longer have to be running the stocker client and you can even uninstall that local Docker 12 00:00:57,080 --> 00:01:03,480 client you'll then run git cloud container clusters get credentials and then whatever your cluster name 13 00:01:03,510 --> 00:01:07,510 is your cluster name is going to be back over on your dashboard. 14 00:01:07,620 --> 00:01:13,940 It'll be whatever name we entered in right there which in this case is ticketing dash def so if you 15 00:01:13,940 --> 00:01:19,700 go through this process you no longer need Docker for desktop on your local machine if you're okay still 16 00:01:19,700 --> 00:01:24,680 running Docker or you still want to have this Docker client around then you will instead run G Cloud 17 00:01:24,680 --> 00:01:31,220 container clusters bla bla bla chances are you're going to fit in this crew or this side over here. 18 00:01:31,280 --> 00:01:36,350 The only reason to go with these stuff on the left hand side is if you really truly are very sure that 19 00:01:36,350 --> 00:01:41,210 you're not going to be running Docker locally anytime soon or if you have space constraints on your 20 00:01:41,210 --> 00:01:43,410 local machine or something like that. 21 00:01:43,670 --> 00:01:47,840 So again chances are you're going to be using this command over here on the right hand side as a matter 22 00:01:47,840 --> 00:01:48,140 of fact. 23 00:01:48,140 --> 00:01:56,130 That's what I'm going to do as well so I to go back over to my terminal and I will run G Cloud container 24 00:01:56,610 --> 00:02:04,140 clusters get dash credentials and then the name of my cluster which as we just saw a moment ago is ticketing 25 00:02:04,200 --> 00:02:05,040 dash dev 26 00:02:09,680 --> 00:02:15,540 so I'll run that and then very quickly it'll pretty much resolve and kicking back to the command line. 27 00:02:15,610 --> 00:02:17,280 So did it work. 28 00:02:17,290 --> 00:02:18,460 Well that's a good question. 29 00:02:18,490 --> 00:02:23,910 I'm going to go back up here to the top right hand side or find my little Docker for desktop icon then 30 00:02:23,910 --> 00:02:29,490 go down to Cuba 90s and you'll notice I now have an additional entry in this little context menu. 31 00:02:29,490 --> 00:02:34,990 So this little entry right here is how I'm going to tell cube Seitel that I want to connect to the Cuban 32 00:02:34,990 --> 00:02:41,160 eddies cluster that is running in Google Cloud if I ever want to use my local cluster instead I can 33 00:02:41,160 --> 00:02:43,510 select Docker desktop instead. 34 00:02:43,560 --> 00:02:45,320 So let me show you this in action. 35 00:02:45,420 --> 00:02:51,300 I'm going to select Docker desktop and then at my terminal I'll do a cube Seitel get pods. 36 00:02:51,620 --> 00:02:57,240 And when I do so you'll see that without a doubt I'm connected to my local cluster my local cluster 37 00:02:57,300 --> 00:03:02,450 has the off pod running which we created that deployment for just a little bit ago. 38 00:03:02,760 --> 00:03:09,150 If I then go back up to this dropdown and select the other context I am now connected through cube Seitel 39 00:03:09,420 --> 00:03:12,110 to the cluster that we just created in Google Cloud. 40 00:03:12,360 --> 00:03:18,690 So I can now do a cube Seitel get pods and you'll see that says no resources found. 41 00:03:18,790 --> 00:03:25,880 That's because the cluster we just made in the cloud is of course running nothing whatsoever so we can 42 00:03:25,880 --> 00:03:29,960 now toggle between these two different clusters very easily if we need to. 43 00:03:29,970 --> 00:03:34,430 Now having said that moving forward in the course really encourage you to keep your mind on this little 44 00:03:34,430 --> 00:03:39,020 menu right here and make sure that you are always connected to the appropriate cluster. 45 00:03:39,050 --> 00:03:43,220 So for right now because I'm still going to show you how to finish up this initial setup of the cluster 46 00:03:43,220 --> 00:03:48,040 in Google Cloud I'm going to leave it on that context but eventually later on after we go through this 47 00:03:48,040 --> 00:03:51,280 good cloud setup I'm going to eventually go back to my local cluster. 48 00:03:51,380 --> 00:03:57,290 And so at some point time I'm going to go here and go back to Docker desktop instead OK. 49 00:03:57,330 --> 00:03:59,840 So this is looking pretty good but we're not quite done yet. 50 00:04:00,300 --> 00:04:05,310 Even though we have connected to this cluster that's running the cloud we still do not have the ability 51 00:04:05,490 --> 00:04:11,780 to tell scaffold to build any of our images using this Google cloud build thing. 52 00:04:11,870 --> 00:04:13,770 So we saw a little bit of setup to do. 53 00:04:13,820 --> 00:04:16,940 Let's take a pause right here and then finish this stuff up in the next video.