Recently I found it intriguing to see the Google announcement of Cloud Run(https://cloud.google.com/run/). I was not sure how it was a different solution as Azure had already demonstrated Serverless Container service using Virtual Kubelet and similarly Amazon has Fargate. So how different is this solution to make PRE’s excited!? I started out exploring the documentation and demoes and then made my own repo to demonstrate how simple it can be.
You can find the source code of the example use case I refer to in this blog here: https://github.com/julianfrank/googlecloudrun
- Google cloud Account
- Basic familiarity with GCloud Console UI
- Basic Understanding of Git and working copy in your workspace
- Account in Github
Step 1: Copy
You can fork this Repository to your Account on github before the below steps
Below is the option you could choose if you want google cloud to store your repo…
Under Connect External Repository select your project where you want to host this repo and the provider as github
You will be asked to authorize with gihub password.. Go ahead and the select the repo where you forked my repo…
Step 2: Understand the next Steps
Let me quickly explain the files in this repo
main.go -> Simple Go file to run a http server on PORT. PORT is an environment variable that Google Cloud Run will share when the container is invoked. The main.go code serves the files in the public folder by default. In this repo the public folder has only one simple index.html file.
Dockerfile-> This is a simple multistage Dockerfile definition that compiles the main.go into the myapp executable. In the final stage it copies the myapp executable and public folder into the final container image that gets built locally. This final stage uses the
alpine scratch layer which results in a really compact and secure <4MB image!
Cloudbuild.yaml-> This file specifies how to CI and CD. Go ahead and replace the $PROJECT_ID with your preferred project if it is not going to be your current project…Also the $REPO_NAME to something more user friendly if needed. But make sure you note down what you change and make suitable changes in further steps accordingly.
Step 3: Setup the Endpoint
Choose “Cloud Run”
Click on “Create Service”
Provide the container url… and service name as per what is specified in the cloudbuild.yaml file. This is important!!
Also Ensure that “Allow unauthenticated invocations” have been ticked..
I also like to reduce the memory to 128MB and Maximum Requests per container to 4 to prevent misuse…
Hit Create and the endpoint should get created…The result will show error as the target image is still not built…We are getting there…
Step 4: Setup the Trigger
Now that the key ingredients are ready, Its time to setup the trigger that will make this whole engine run on its own…
Goto Cloud Build and Select the Triggers Option
Click on add Trigger
Choose the Cloud Source Repository
Now Give the Trigger a name…Leave everything on default…Change the Build Configuration to “Cloud Build Configuration file”. This will tell the trigger to proceed and take the next steps as per the cloudbuild.yaml file definitions.
Now click on “Create Trigger”
You should now see the trigger listed
You can activate the trigger manually using the “Run Trigger” Option… Let’s hit it!
The History will now show the status of the build process…now go to the Cloud Run Dashboard and you should find the endpoint with the url associated with it…
Click on this url and you should see your sample html page
Now Go back to your github repo and change the code… you will see the build triggers the instant you commit and push the code back to the repository…
In summary the whole initial planning and preparation is still time consuming but once setup, everything is fluid and painless.
As of Now (may2019) the cloudbuild.yaml is unable to build the endpoint with public unauthorized access enabled endpoints… This while great for internal only apps … Is a bad thing for public facing web page / API based solutions. Hopefully it gets ironed out by the time Cloud Run becomes GA.