1 00:00:00,001 --> 00:00:01,367 [No Audio] 2 00:00:01,367 --> 00:00:03,934 Hello, and welcome back to the Container Masterclass, 3 00:00:03,934 --> 00:00:07,167 or as we very informally call it, the CMC. 4 00:00:07,434 --> 00:00:10,167 As you may remember from many, many videos of this 5 00:00:10,167 --> 00:00:14,034 course, this is the Google Cloud dashboard. 6 00:00:14,467 --> 00:00:18,134 Cloud Run is a part of Google Cloud Platform offerings. 7 00:00:18,134 --> 00:00:21,967 So much like Google Compute Engine VMs, or GKE's 8 00:00:21,967 --> 00:00:27,734 Hosted Kubernetes, the way to navigate is through the hamburger icon. 9 00:00:27,734 --> 00:00:29,767 Before we start using Cloud Run, 10 00:00:29,767 --> 00:00:32,401 we need to make sure that we have enabled its 11 00:00:32,401 --> 00:00:37,467 API in our GCP project. Go to APIs & Services, 12 00:00:37,767 --> 00:00:41,167 click on Dashboard, and you will find stats about 13 00:00:41,167 --> 00:00:44,434 a list of APIs relevant to the products used 14 00:00:44,434 --> 00:00:48,334 under your GCP project. It shows that we have had 15 00:00:48,334 --> 00:00:51,001 the most requests made to Compute Engine and 16 00:00:51,001 --> 00:00:55,367 Logging APIs, which makes sense because both GCE 17 00:00:55,367 --> 00:00:59,001 VMs and GKE Clusters are hosted using Compute 18 00:00:59,001 --> 00:01:04,601 Engine VMs. To find the Cloud Run API, let's head to the Library tab. 19 00:01:05,934 --> 00:01:07,534 You can see a bunch of APIs 20 00:01:07,534 --> 00:01:10,601 divided by categories of usage, we don't want to 21 00:01:10,601 --> 00:01:13,734 keep scrolling for eternity. So let's use one of 22 00:01:13,734 --> 00:01:16,301 the best inventions of computer science, 23 00:01:16,534 --> 00:01:20,434 the search function. Type Cloud Run, and the first 24 00:01:20,434 --> 00:01:24,701 result, you see should be our target API. In case 25 00:01:24,701 --> 00:01:27,701 you get some different results. You can remember 26 00:01:27,701 --> 00:01:30,734 this little icon which looks like a stylized play 27 00:01:30,734 --> 00:01:33,134 or forward button for music player. 28 00:01:33,867 --> 00:01:36,301 Once you land on the Cloud Run API page, 29 00:01:36,701 --> 00:01:38,001 you can notice a lot of 30 00:01:38,001 --> 00:01:41,801 details like when the API was last updated, or 31 00:01:42,167 --> 00:01:45,567 it's one liner description, or its overview, or 32 00:01:45,567 --> 00:01:49,301 even links to its documentation and some Quickstart tutorials. 33 00:01:50,067 --> 00:01:51,634 Let's take a relaxing breath 34 00:01:51,634 --> 00:01:54,867 for a moment and look at an overview of the Cloud Run. 35 00:01:55,801 --> 00:01:59,101 This is important because this is how Google 36 00:01:59,101 --> 00:02:04,267 describes and wants us to perceive Cloud Run as a product. 37 00:02:05,067 --> 00:02:07,267 It is a managed compute platform. 38 00:02:07,667 --> 00:02:11,667 Of course, because as we mentioned, it does run on a 39 00:02:11,667 --> 00:02:16,167 Kubernetes Cluster in the backend. It enables you 40 00:02:16,167 --> 00:02:19,434 to run stateless application containers invokable 41 00:02:19,434 --> 00:02:24,401 via HTTP APIs. HTTP APIs are fine, because 42 00:02:24,401 --> 00:02:26,634 everything that we have done so far in this 43 00:02:26,634 --> 00:02:31,034 course, has used HTTP requests in one way or another. 44 00:02:31,267 --> 00:02:35,934 But the most crucial detail here is stateless. 45 00:02:36,501 --> 00:02:39,267 Cloud Run as of recording this video in 46 00:02:39,267 --> 00:02:43,634 November 2020, only allows stateless applications. 47 00:02:43,767 --> 00:02:49,534 So no StatefulSets, but deployments are 48 00:02:49,534 --> 00:02:52,567 stateless, so we should be able to play with them. 49 00:02:54,234 --> 00:02:57,067 Rest of the part says how it abstracts away the 50 00:02:57,067 --> 00:03:00,267 infrastructure management. We have already seen 51 00:03:00,267 --> 00:03:04,067 that in the last lecture so let's enable the API. 52 00:03:04,067 --> 00:03:06,267 [No Audio] 53 00:03:06,267 --> 00:03:09,267 The API is ready. It is showing some previous 54 00:03:09,267 --> 00:03:12,267 traffic because I had used it for testing earlier. 55 00:03:13,234 --> 00:03:17,601 Now, let's head back to Cloud Run through the hamburger icon. 56 00:03:17,601 --> 00:03:20,334 [No Audio] 57 00:03:20,334 --> 00:03:22,667 The list of services is empty, 58 00:03:22,667 --> 00:03:25,501 since this would be your first time using it. 59 00:03:25,767 --> 00:03:29,601 The API is ready, and we can start creating our first 60 00:03:29,601 --> 00:03:31,834 Cloud Run service in the next lecture. 61 00:03:32,101 --> 00:03:35,834 Till then, happy learning and I hope you have a great day.