WEBVTT 00:00.960 --> 00:01.793 -: In the last section 00:01.793 --> 00:05.430 we created our first Kubernetes cluster on Google Cloud. 00:05.430 --> 00:06.263 In this section, 00:06.263 --> 00:08.076 I wanna very quickly walk through this dashboard 00:08.076 --> 00:11.010 and show you a couple of interesting pieces, 00:11.010 --> 00:13.290 some different things that are going to be relevant later on 00:13.290 --> 00:16.020 as we start to actually deploy our application. 00:16.020 --> 00:18.170 The first thing I want to do is click on the multi-cluster 00:18.170 --> 00:20.160 right here that we just created. 00:20.160 --> 00:21.958 On this panel, you'll see some information 00:21.958 --> 00:24.870 about the configuration of our cluster. 00:24.870 --> 00:27.630 Now, it's not super common for you to have to come in here 00:27.630 --> 00:29.040 and reference information, 00:29.040 --> 00:31.170 but you will see some interesting stuff in here 00:31.170 --> 00:33.420 that you might need to make use of at some point in time 00:33.420 --> 00:34.620 in the future. 00:34.620 --> 00:35.790 Toward the bottom of this page, 00:35.790 --> 00:37.704 you're gonna see information about the different nodes 00:37.704 --> 00:40.260 that are in use in our cluster. 00:40.260 --> 00:42.570 And so if you ever need to change the specs 00:42.570 --> 00:43.740 on the different nodes here, 00:43.740 --> 00:47.040 for example, add memory or add a more powerful CPU, 00:47.040 --> 00:49.560 you can do it from this interface here. 00:49.560 --> 00:52.200 Now, besides showing information about the cluster, 00:52.200 --> 00:54.346 you'll also notice that there's a couple of different tabs 00:54.346 --> 00:56.460 on the left hand side. 00:56.460 --> 00:58.710 We can check out workloads right here. 00:58.710 --> 01:01.020 This is going to be a page that's going to eventually show 01:01.020 --> 01:03.090 all the different pods and deployments 01:03.090 --> 01:05.160 that belong to our application. 01:05.160 --> 01:07.620 At present, we have nothing running on our cluster, 01:07.620 --> 01:10.050 so this window is completely empty. 01:10.050 --> 01:11.760 We then have the services tab, 01:11.760 --> 01:12.593 as you might guess, 01:12.593 --> 01:14.460 this is all about different services 01:14.460 --> 01:15.784 that we create inside of our cluster, 01:15.784 --> 01:17.910 like the ClusterIP service, 01:17.910 --> 01:20.670 or a load balancer if we create one, 01:20.670 --> 01:23.430 or the NodePort services, all that kind of stuff 01:23.430 --> 01:25.170 you're all going to see eventually show up 01:25.170 --> 01:27.150 on the services tab. 01:27.150 --> 01:28.860 Now, applications right here, 01:28.860 --> 01:31.800 is really talking about different kind of plugins 01:31.800 --> 01:34.830 that we can install and make use of inside of our cluster. 01:34.830 --> 01:37.080 So this is not talking about different pods 01:37.080 --> 01:38.400 or deployments that we're running, 01:38.400 --> 01:40.470 this is talking about some third party software 01:40.470 --> 01:42.360 that might run inside of our cluster. 01:42.360 --> 01:44.640 We're not going to make use of any third party stuff 01:44.640 --> 01:47.583 so we are going to generally ignore the applications tab. 01:48.540 --> 01:50.100 The configuration is gonna show 01:50.100 --> 01:52.830 all the different environment variables or secrets, 01:52.830 --> 01:54.960 that we set up inside of our cluster. 01:54.960 --> 01:57.360 You'll recall that we have one secret in use right now, 01:57.360 --> 01:59.760 which stores our Postgres password. 01:59.760 --> 02:01.650 So eventually,. we're gonna see that secret appear 02:01.650 --> 02:03.063 on this configuration tab. 02:03.990 --> 02:05.310 Then finally, storage 02:05.310 --> 02:08.160 is going to list all of the different persistent volumes 02:08.160 --> 02:09.750 and persistent volumes claims 02:09.750 --> 02:12.210 that are set up inside of our cluster. 02:12.210 --> 02:13.800 One quick thing I want to remind you about, 02:13.800 --> 02:15.780 lemme see if I have the diagram up for it, 02:15.780 --> 02:16.680 here it is, right here. 02:16.680 --> 02:18.120 All right, this is the diagram that we looked at 02:18.120 --> 02:20.730 a long time ago when we were talking about 02:20.730 --> 02:23.610 persistent volumes and persistent volume claims. 02:23.610 --> 02:26.883 You'll recall that we had said that on your local computer, 02:28.050 --> 02:31.290 we had a default provider for storage, 02:31.290 --> 02:33.300 and on your computer, Kubernetes said, 02:33.300 --> 02:35.550 okay, I'm gonna take a slice of your hard drive 02:35.550 --> 02:37.740 and dedicate it to a persistent volume. 02:37.740 --> 02:39.570 That was what was happening on your computer. 02:39.570 --> 02:41.190 Remember, the entire point of that discussion 02:41.190 --> 02:43.680 was to say that the environment that Kubernetes 02:43.680 --> 02:45.330 is running in is going to assign 02:45.330 --> 02:48.180 different default classes of storage. 02:48.180 --> 02:50.580 And so we had also said that on a cloud provider, 02:50.580 --> 02:54.510 if we tell Kubernetes that we need one gigabyte of storage, 02:54.510 --> 02:56.490 then Kubernetes is going to try to select 02:56.490 --> 02:57.900 from one of these different services 02:57.900 --> 03:00.360 that is provided by our cloud provider. 03:00.360 --> 03:01.860 So in the case of Google Cloud, 03:01.860 --> 03:03.510 our default storage provider 03:03.510 --> 03:06.330 is called Google Cloud Persistent Disk. 03:06.330 --> 03:08.730 And in fact, if you go back over here to the storage tab, 03:08.730 --> 03:11.400 and then look at storage classes, 03:11.400 --> 03:14.430 you'll see that we have one storage class called Standard, 03:14.430 --> 03:17.610 this is our default, and if I click into it, 03:17.610 --> 03:19.350 you'll see somewhere around here, 03:19.350 --> 03:20.790 maybe not on this page so much, 03:20.790 --> 03:22.380 but definitely back on this page, 03:22.380 --> 03:25.770 you'll notice that it says GCE-PD right there. 03:25.770 --> 03:28.920 So PD stands for Persistent Disk. 03:28.920 --> 03:30.633 And if we Google that right now, 03:32.370 --> 03:34.590 Google Cloud Persistent Disk. 03:34.590 --> 03:36.870 Yep, this is the offering from Google Cloud 03:36.870 --> 03:40.110 to reliably store some information consistently 03:40.110 --> 03:42.480 and not have it be kind of wiped away magically 03:42.480 --> 03:43.920 at some point in time. 03:43.920 --> 03:45.390 So as we had said before, 03:45.390 --> 03:47.280 because we are now in Google Cloud 03:47.280 --> 03:48.600 some of these default options 03:48.600 --> 03:49.950 that Kubernetes is going to use 03:49.950 --> 03:51.360 are going to be slightly different 03:51.360 --> 03:53.730 than what the defaults are on your local machine. 03:53.730 --> 03:56.370 And looking at the persistent storage is a great place 03:56.370 --> 03:58.440 to kind get an idea of the fact that, 03:58.440 --> 03:59.580 yeah, now that we're in the cloud, 03:59.580 --> 04:01.500 things are a little bit different. 04:01.500 --> 04:04.560 Okay, so that's pretty much it for Kubernetes engine, 04:04.560 --> 04:05.700 this dashboard right here. 04:05.700 --> 04:07.590 Now, we are going to come back to the dashboard 04:07.590 --> 04:10.590 several times and do a couple different things, 04:10.590 --> 04:13.900 but for right now we're gonna start to focus on 04:15.660 --> 04:17.460 adding a deployment script to our repo, 04:17.460 --> 04:19.590 that's gonna be our travis.yml file. 04:19.590 --> 04:21.120 We're gonna make sure that everything 04:21.120 --> 04:23.769 is set up to automatically deploy our application 04:23.769 --> 04:25.710 off to this Kubernetes cluster 04:25.710 --> 04:27.780 as soon as we push and merge our code 04:27.780 --> 04:30.270 on the master branch of our GitHub Repo. 04:30.270 --> 04:31.950 So quick pause, and we're gonna start that 04:31.950 --> 04:32.973 in the next section.