This page shows you how to deploy a sample container that has already been uploaded to the Container Registry repository to Cloud Run.
Before you begin
Sign in to your Google Account.
If you don't already have one, sign up for a new account.
In the Cloud Console, on the project selector page, select or create a Cloud project.
Projeniz için faturalandırmanın etkinleştirildiğinden emin olun.
Deploying the sample container
To deploy a container:
Click Create service to display the Create service form:
In the form,
Select Cloud Run (fully managed) as your development platform.
Select the region where you want your service located.
Specify the name you want to give to your service.
Select Allow unauthenticated invocations to be able to open the result in your web browser
Click Next to continue to the second page of the service creation form:
In the form,
gcr.io/cloudrun/helloas a container image.
Click Create to deploy the image to Cloud Run and wait for the deployment to finish.
Click the displayed URL link to run the deployed container.
Cloud Run locations
Cloud Run is regional, which means the infrastructure that
runs your Cloud Run services is located in a specific region and is
managed by Google to be redundantly available across
all the zones within that region.
Meeting your latency, availability, or durability requirements are primary
factors for selecting the region where your Cloud Run services are run.
You can generally select the region nearest to your users but you should consider
the location of the other Google Cloud
products that are used by your Cloud Run service.
Using Google Cloud products together across multiple locations can affect
your service's latency as well as cost.
Cloud Run is available in the following regions:
If you already created a Cloud Run service, you can view the region in the Cloud Run dashboard in the Cloud Console.
Congratulations! You have just deployed to Cloud Run a container that responds to incoming web requests. Cloud Run automatically scales your container up to handle the received requests, then scales down when demand decreases. You only pay for the CPU, Memory and Networking consumed during request handling.
To learn how to build a container from code source, push to Container Registry, and deploy, see: