Getting Started with Google Cloud Run V2

This guide provides a step-by-step tutorial on how to get started with Google Cloud Run V2.

Hafeez Baig
|
38 steps
|
4 minutes

Google Cloud

Type **Cloud Run** in the search bar and click on the **Cloud Run** option.

**What is Cloud Run?**\ \ **Cloud Run** is a fully managed serverless compute platform on Google Cloud that allows you to run containerized applications in a scalable and cost-efficient way. You deploy your containers, and Cloud Run automatically handles scaling, load balancing, and infrastructure management. It provides pay-as-you-go pricing, scaling from zero to hundreds or thousands of instances based on demand, and supports both HTTP-triggered and background processing tasks.

**Cloud Run** wizard will open, click on the **Write a function** button on the top left side

**Create service** wizard will open, select the option **Deploy one revison from an existing container image**

Scroll to the **Container image URL** section and click on the **SELECT** button

On the right side **Select container image** wizard will open, click on the **Demo containers** dropdown option

Select the option **hello**

Click on the **SELECT** button

Scroll to the **Service name** section and type "**my-first-cloud-run-service**"

Scroll to the **Authentication** section and select the **Allow public access** radio button

**What is the Allow unauthenticated invocations option in Authentication?**\ \ The **Allow unauthenticated invocations** option in **Authentication** enables public access to your Cloud Function, meaning that it can be invoked by anyone without requiring authentication. This is useful for publicly accessible functions like webhooks or APIs but may expose the function to unauthorized use if not properly secured.

Scroll to the **Billing** section and select the **Request based** radio button

**What is CPU is only allocated during request processing option?**\ \ The **CPU is only allocated during request processing** option in Cloud Run means that the CPU resources are provided only while the application is actively handling requests. When there are no incoming requests, CPU allocation is reduced to minimize costs. This option helps optimize resource usage and billing by ensuring that you only pay for CPU time when your application is actively processing data.

Scroll to the **Maximum number of instances** text input field and enter "**0**"

**What is the Minimum number of instances option in Service autoscaling?**\ \ The **Minimum number of instances** option in **Service autoscaling** specifies the minimum number of instances that should be running for a service at all times, regardless of the current traffic or load. This setting ensures that there is always a baseline level of capacity available to handle incoming requests, which helps maintain performance and reduce latency during periods of low or no traffic.

Scroll to the **Ingress control** section and select the **All** radio button

**What is Ingress control?**\ \ **Ingress control** refers to the management and configuration of how incoming network traffic is allowed to access services or applications within a cloud environment. It involves setting rules and policies for routing, load balancing, and securing external requests that reach your applications. Ingress control helps ensure that traffic is properly directed, balanced, and protected from unauthorized access or attacks.

Scroll the page and click on the **CREATE** button

Congratulations! on successfully creating a Service in the Google Cloud Run!

**my-first-cloud-run-service** wizard will open, click on the copy widget to copy the **URL** on the left side

Open the new tab in any browser

Paste the copied URL

**It's running** wizard will open

Congratulations the Google Cloud Run is Up and Running!

Go back to the **my-first-cloud-run-service** wizard

Click on the **Observability** tab on the left side. here you can view all the graph updates and metrics **Note:** The metrics will take some time to load up.

**What are METRICS?**\ \ **Metrics** are quantitative measurements used to assess, monitor, and track the performance, behavior, and health of systems, applications, and processes. They provide data points such as CPU usage, memory consumption, request latency, and error rates, helping you understand and optimize system performance, identify issues, and ensure efficient operation.

Click on the **Logs** tab on the left side bar, here you can view all the Logs for the Cloud Run Service.

**What are Logs?**\ \ **Logs** are records of events, actions, and transactions generated by applications, systems, and services. They provide detailed information about the operational behavior and status of software and infrastructure, including errors, warnings, and informational messages. Logs are crucial for monitoring, troubleshooting, and analyzing performance, helping to identify issues and understand system behavior.

Click on the **TRIGGERS** tab, here you can view the Eventrac Triggers or add new Triggers

**What are TRIGGERS?**\ \ **Triggers** are events or conditions that initiate the execution of predefined actions or workflows in response to specific occurrences. In cloud computing, triggers can automatically start processes such as running a function, sending notifications, or updating data based on predefined criteria. For example, a trigger might initiate a Cloud Function when a file is uploaded to a storage bucket or when a database record is modified.

Click on the **NETWORKING** tab, here you can view the Ingress Control and VPC Configurations for the Cloud Run

**What is NETWORKING?**\ \ **Networking** refers to the design, implementation, and management of the connections and communications between different systems and resources within a cloud environment. In GCP, networking encompasses the setup and configuration of Virtual Private Cloud (VPC) networks, subnets, IP addresses, firewalls, load balancers, and routing rules. It ensures secure and efficient data transfer, connectivity, and access between cloud services, applications, and external networks.

Click on the **SECURITY** tab, here you can view all the Security Configurations for the Cloud Run

**What is SECURITY?**\ \ **Security** in the context of cloud computing refers to the measures and practices implemented to protect data, applications, and infrastructure from unauthorized access, threats, and vulnerabilities. In GCP, security includes configuring access controls, encryption, identity and access management (IAM), network security, and compliance with regulations. It ensures the confidentiality, integrity, and availability of resources while safeguarding against data breaches and cyberattacks.

Click on the **YAML** tab, here you can view the YAML format code

**What is YAML?**\ \ **YAML** (YAML Ain't Markup Language) is a human-readable data serialization format used for configuration files and data exchange. It is designed to be easy to read and write, with a structure based on indentation and simple syntax. YAML is commonly used in cloud computing and DevOps for defining configurations, such as Kubernetes manifests, CI/CD pipelines, and application settings. It supports complex data structures like lists and dictionaries while maintaining clarity and readability.

Click on the **EDIT & DEPLOY NEW REVISION** button on the top left side

**Deploy revision to my-first-cloud-run-service** wizard will open, scroll to the **Containers** section and here you can edit the **Container** Configurations

Scroll to the **Request** tab, here you can edit the **Requests** Configurations

Scroll to the **Cloud SQL connections** section, here you can view or add new Cloud SQL connections

Untick the checkbox **Serve this revision immediately**

**What is Serve this revision immediately checkbox?**\ \ The **Serve this revision immediately** checkbox, when deploying or updating a service in Google Cloud Run or similar platforms, allows the newly deployed revision of your application to start handling requests immediately. Selecting this option ensures that the new revision is activated and replaces the previous one without delay, facilitating instant updates and reducing the time between deployment and live service availability.

Click on the **DEPLOY** button

On the **my-first-cloud-run-service** wizard, you can view a new Name **my-first-cloud-run-service-00002-I6g** **Note:** It is created by the Cloud Run

To Manage and Route the Traffic, click on the **MANAGE TRAFFIC** button on the top left side

On the right side **Manage traffic** wizard will open, here you can allocate and distribute the traffic between different revisions

On the top left corner click on the **Cloud Run** to go to the Dashboard

**Services** wizard will open, to delete a Service select the Name **my-first-cloud-run-service**

Click on the **DELETE** button on the top left side

**Delete my-first-cloud-run-service** wizard will open, click on the **DELETE** button Note: The deletion of the Cloud Run Service will take some time.

Congratulations! on completing this lab and Getting Started with Google Cloud Run V2