WEBVTT 00:00.780 --> 00:02.310 -: In last section, we started talking about 00:02.310 --> 00:04.110 how we're going to take our Kubernetes cluster 00:04.110 --> 00:06.960 and eventually move it over to a production environment. 00:06.960 --> 00:08.940 We just spoke about some aspects of billing. 00:08.940 --> 00:11.220 I now want to give you just a quick couple notes 00:11.220 --> 00:13.620 on why we are making use of Google Cloud 00:13.620 --> 00:15.540 for deploying this Kubernetes application 00:15.540 --> 00:18.210 as opposed to AWS, because after all, 00:18.210 --> 00:20.880 we did make use of AWS earlier on in this course 00:20.880 --> 00:23.580 so it's a little bit strange to swap providers out 00:23.580 --> 00:26.190 halfway through in the context of the course. 00:26.190 --> 00:27.900 But again, we're doing this for a very good reason 00:27.900 --> 00:30.690 so let me lay out a couple reasons why we are swapping 00:30.690 --> 00:31.773 over to Google Cloud. 00:33.030 --> 00:35.340 So here's my very quick checklist here. 00:35.340 --> 00:37.170 Now, before I talk about any of these points, 00:37.170 --> 00:38.850 I want you to just understand 00:38.850 --> 00:41.070 that these are my subjective opinions 00:41.070 --> 00:43.740 on why you might want to use Google Cloud for Kubernetes 00:43.740 --> 00:45.990 over AWS right now. 00:45.990 --> 00:47.610 These are entirely subjective 00:47.610 --> 00:50.280 so people are completely free to disagree with me. 00:50.280 --> 00:51.113 No problem there. 00:51.113 --> 00:53.400 I don't mind if you disagree one bit. 00:53.400 --> 00:54.930 Totally fine if you do. 00:54.930 --> 00:58.260 So, we're going to be making use of Google Cloud over AWS 00:58.260 --> 01:00.540 for these couple reasons right here. 01:00.540 --> 01:03.630 First reason, Google created Kubernetes. 01:03.630 --> 01:05.490 They created the open source project 01:05.490 --> 01:07.800 and they supported the project financially 01:07.800 --> 01:10.950 for the first couple years of its existence. 01:10.950 --> 01:13.920 That means to me that Google as an organization 01:13.920 --> 01:17.550 has a lot of experience with Kubernetes, and they understand 01:17.550 --> 01:21.270 at a very low level why it works and what its purpose is. 01:21.270 --> 01:24.030 And so even though the people who created Kubernetes 01:24.030 --> 01:26.940 are probably not the same people who set up Kubernetes 01:26.940 --> 01:29.160 or all the infrastructure for it on Google Cloud, 01:29.160 --> 01:30.960 there's still a very good reason there to believe 01:30.960 --> 01:33.630 that there was at least a little bit of knowledge transfer. 01:33.630 --> 01:36.690 So essentially, the people who set up Kubernetes 01:36.690 --> 01:38.460 on Google Cloud probably had access 01:38.460 --> 01:41.940 to some people with very low level knowledge of Kubernetes 01:41.940 --> 01:44.460 and they probably understand very well how it works. 01:44.460 --> 01:46.320 Again, totally subjective. 01:46.320 --> 01:49.470 I could be totally wrong, but that's gonna be kinda like... 01:49.470 --> 01:51.300 It's just my opinion. 01:51.300 --> 01:52.739 Now, the rest of the reasons on here 01:52.739 --> 01:55.260 are a little bit more objective than that one. 01:55.260 --> 01:57.960 So the next one, AWS only somewhat recently 01:57.960 --> 01:59.370 got Kubernetes support. 01:59.370 --> 02:01.260 That's in early 2018. 02:01.260 --> 02:04.380 Now, you might be watching this video in 2019, 2020 02:04.380 --> 02:07.350 or even later, and maybe at some point in time, 02:07.350 --> 02:10.440 AWS will catch up with Google Cloud's implementation, 02:10.440 --> 02:13.950 but as it stands right now, the UI and the interface 02:13.950 --> 02:17.400 for manipulating Kubernetes clusters on AWS 02:17.400 --> 02:19.710 leaves a little bit to be wanted. 02:19.710 --> 02:21.390 Like it's not that great, 02:21.390 --> 02:23.730 it's not that easy to use right now. 02:23.730 --> 02:28.200 So using Kubernetes from a UI perspective on Google Cloud, 02:28.200 --> 02:30.450 far easier, much, much easier, 02:30.450 --> 02:31.800 far easier to get started with 02:31.800 --> 02:34.320 because they've had a number of years to iterate 02:34.320 --> 02:36.753 on this product ahead of AWS. 02:38.280 --> 02:41.310 Next up, it is far easier to kind of mess around 02:41.310 --> 02:43.470 with Kubernetes than on, or excuse me, 02:43.470 --> 02:45.930 far easier to mess around Kubernetes on Google Cloud 02:45.930 --> 02:47.640 than it is on AWS. 02:47.640 --> 02:50.610 So on Google Cloud, we get something called a cloud console 02:50.610 --> 02:53.760 which is essentially a terminal instance connected directly 02:53.760 --> 02:58.530 to your entire VPC of sorts hosted on Google Cloud. 02:58.530 --> 03:00.090 And so you get direct access 03:00.090 --> 03:03.270 to a QCTL command line tool that's wired up 03:03.270 --> 03:05.400 to your production Kubernetes instance 03:05.400 --> 03:07.980 and we'll actually take a look at that in just a little bit. 03:07.980 --> 03:10.650 And so using this tool, you can very easily run 03:10.650 --> 03:15.420 all the same exact commands like say QCTL get pods. 03:15.420 --> 03:17.100 You can run all these same commands 03:17.100 --> 03:20.040 in a production environment that we've been running locally 03:20.040 --> 03:20.873 and on Google Cloud, 03:20.873 --> 03:24.480 that is extremely easy to set up and very easy to do. 03:24.480 --> 03:27.840 Now, you can certainly set up the same system on AWS, 03:27.840 --> 03:31.860 but it's far more involved, much, much, much more involved. 03:31.860 --> 03:33.720 Really easy to get started just poking around 03:33.720 --> 03:37.170 with things on Google Cloud than it is on AWS. 03:37.170 --> 03:38.850 And then finally, in my opinion, again, 03:38.850 --> 03:41.880 these are some subjective elements here. 03:41.880 --> 03:44.550 In my opinion, the documentation around Kubernetes 03:44.550 --> 03:48.900 on Google Cloud is like light years ahead 03:48.900 --> 03:50.913 of the AWS documentation. 03:51.900 --> 03:54.210 Take my word for it, to a certain degree here, 03:54.210 --> 03:57.780 I am in the business of teaching people that stuff. 03:57.780 --> 03:59.190 I'm teaching you right now how to make use 03:59.190 --> 04:00.870 of Docker in Kubernetes. 04:00.870 --> 04:03.030 To a degree, I like to imagine 04:03.030 --> 04:04.290 that I've got a good understanding 04:04.290 --> 04:06.900 of what documentation is, and in my opinion, 04:06.900 --> 04:09.690 the Google Cloud documentation is just head and shoulders 04:09.690 --> 04:13.530 above the AWS documentation for Kubernetes right now. 04:13.530 --> 04:15.900 So take that for what you will. 04:15.900 --> 04:16.733 So that's it. 04:16.733 --> 04:17.820 That's the four reasons that we're making use 04:17.820 --> 04:19.140 of Google Cloud for this stuff. 04:19.140 --> 04:21.570 I just wanted to be very clear about these reasons. 04:21.570 --> 04:23.610 I wouldn't normally kinda list these out 04:23.610 --> 04:26.010 or iterate them out, except in this case, 04:26.010 --> 04:28.140 we made use of AWS earlier in the course 04:28.140 --> 04:30.570 and so again, it is kind of strange to swap off 04:30.570 --> 04:32.760 to another cloud provider halfway through. 04:32.760 --> 04:33.750 But again, I really think 04:33.750 --> 04:36.990 that there is very good reason to do this swap off. 04:36.990 --> 04:40.200 Much easier to get started with Kubernetes on Google Cloud. 04:40.200 --> 04:42.210 So enough of this, let's take a quick pause right here 04:42.210 --> 04:45.150 and we're gonna get started in our next section 04:45.150 --> 04:46.980 with our production deployment by setting up 04:46.980 --> 04:50.220 a GitHub repository and pushing our code up to it. 04:50.220 --> 04:52.670 So quick pause and I'll see you in just a minute.