Published on: November 19, 2019
4 min read
Discover how we're making it easier to deploy serverless workloads on-premise with Anthos.

This week at Google Cloud Next ’19 UK, Google Cloud grew its Anthos product portfolio with the addition of Cloud Run for Anthos running on-prem. I’m excited to share that GitLab has been collaborating with Google Cloud product teams to support this launch and enable customers with CI/CD and GitLab Serverless capabilities for quicker and easier adoption of serverless solutions. In the spirit of our partnership, our support for Cloud Run for Anthos is a continuation of our collaboration announced earlier this year at Google Cloud Next ’19 in San Francisco, where we showed how you can deploy a serverless function to Cloud Run using the same developer workflow you’re already familiar with in GitLab. Now, we’re looking to bring that same UX and workflow consistency to Cloud Run deployments on Anthos running on-premise. Overall, together, GitLab and Google Cloud are aiming to lower the barrier of adoption for customers looking to architect scalable, cloud native solutions.
However, when discussing cloud native, oftentimes ‘public cloud infrastructure’ comes to mind. But when I think of cloud native, I think of the various, modern ways of architecting scalable solutions, backed by managed services to make operations more convenient. Until very recently, infrastructure-centric managed services like Google Kubernetes Engine (GKE), Cloud Run, StackDriver, etc. have been traditionally associated with workloads running within cloud data centers. Given the recent announcements of Google Cloud Anthos, Google is clearly broadening the boundaries of cloud native across hybrid and heterogeneous environments, including customer data centers. As the infrastructure landscape diversifies, as application development intertwines with abstraction layers of managed services, and as workload flexibility becomes inherent with microservice containerization, the one thing you can rely on staying consistent is GitLab’s developer workflow to supplement all the above. In the context of all things serverless, let's take a closer look at what’s available today, what we’re still working on, and what that means for our users.
GitLab serves as a single application for all of DevOps, which includes building, deploying, and managing serverless applications. GitLab serverless enables developers to focus on writing application code without having to worry about Kubernetes or Knative YAML configuration. GitLab provides templates allowing developers to easily build and deploy Knative services that can be deployed to Cloud Run. Here is a quick video walkthrough on the anatomy of a serverless project hosted in GitLab and deployed to Knative. With Google, you have a few options on how to leverage Cloud Run as a deployment target for GitLab CI/CD. As of this week, you can run Cloud Run in three different flavors:
serverless.yml file within the root of your source code repository to define and deploy to Cloud Run.If you’re interested in getting started with some sample code, check out our documentation and sample app project for reference. Additionally, here is a walkthrough of deploying a demo app to Cloud Run from GitLab. If you’re looking to get started with Serverless on Google Cloud Platform, sign up for GitLab.com here and then sign up for $200 additional free GCP credits.
Enjoyed reading this blog post or have questions or feedback? Share your thoughts by creating a new topic in the GitLab community forum.
Share your feedback