Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://cloud.google.com/functions/docs/configuring/max-instances below:

Set maximum instances for services | Cloud Run Documentation

This page describes how to set the maximum number of instances that can be used for your Cloud Run service using the default Cloud Run autoscaling behavior. To manually scale your service, see Manual scaling.

Specifying maximum instances in Cloud Run lets you limit the scaling of your service in response to incoming requests, although this maximum setting can be exceeded for a brief period due to circumstances such as traffic spikes.

You can use this setting as a way to control your costs or to limit the number of connections to a backing service, such as to a database.

For information about the maximum instance limits that might apply to your service, refer to Maximum instances limits.

For more information on the way Cloud Run autoscales container instances, refer to Instance autoscaling.

Preview — Service-level maximum instances for Cloud Run services

This feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the Service Specific Terms. Pre-GA features are available "as is" and might have limited support. For more information, see the launch stage descriptions.

You can configure maximum instances at the service level or at the revision level. Google recommends that you use service-level maximum instances unless you have a specific need to limit instances at the revision level.

When applying maximum instances, the settings go into effect as follows:

• Service-level: immediately
• Revision-level: upon deployment of the revision

Tagged revisions are started, but only count toward the service-level maximum instances if they are a part of a traffic split.

To get the permissions that you need to configure and deploy Cloud Run services, ask your administrator to grant you the following IAM roles:

• Cloud Run Developer (roles/run.developer) on the Cloud Run service
• Service Account User (roles/iam.serviceAccountUser) on the service identity

For a list of IAM roles and permissions that are associated with Cloud Run, see Cloud Run IAM roles and Cloud Run IAM permissions. If your Cloud Run service interfaces with Google Cloud APIs, such as Cloud Client Libraries, see the service identity configuration guide. For more information about granting roles, see deployment permissions and manage access.

You can change the maximum instances setting using the Google Cloud console, the Google Cloud CLI, or a YAML file when you create a new service or deploy a new revision.

1. In the Google Cloud console, go to Cloud Run:

   Go to Cloud Run

2. If you are configuring a new service, select Services and click Deploy container to display the Create service form. Locate the Service scaling form.

3. If you are configuring an existing service, click the service to display its detail panel, then click the edit Edit service level scaling settings at the top right of the detail panel.

4. In the field labelled Maximum number of instances, specify the required maximum number of container instances, using any integer value from 1 to the maximum limit possible for your service.

5. Click Create for a new service or Deploy for an existing service.

You can update the maximum number of instances of a given service by using the following command:

gcloud beta run services update SERVICE --max MAX-VALUE

Replace the following:

• SERVICE: the name of your service.
• MAX-VALUE: the required maximum number of container instances, using any integer value from 1 to the maximum limit possible for your service.

You can also set the maximum number of instances during deployment using the command:

gcloud beta run deploy --image IMAGE_URL --max MAX-VALUE

Replace the following:

• IMAGE_URL: a reference to the container image, for example, us-docker.pkg.dev/cloudrun/container/hello:latest. If you use Artifact Registry, the repository REPO_NAME must already be created. The URL follows the format of LOCATION-docker.pkg.dev/PROJECT_ID/REPO_NAME/PATH:TAG .
• MAX-VALUE: the required maximum number of container instances, using any integer value from 1 to the maximum limit.

Any configuration change leads to the creation of a new revision. Subsequent revisions will also automatically get this configuration setting unless you make explicit updates to change it.

1. If you are creating a new service, skip this step. If you are updating an existing service, download its YAML configuration:

   gcloud run services describe SERVICE --format export > service.yaml

2. Update the run.googleapis.com/maxScale: attribute:

   apiVersion: serving.knative.dev/v1
   kind: Service
   metadata:
     name: SERVICE
     annotations:
       run.googleapis.com/launch-stage: BETA
       run.googleapis.com/maxScale: 'MAX-INSTANCE'

   Replace the following:

   • SERVICE: the name of your Cloud Run service
   • MAX-INSTANCE: the required maximum number of container instances, using any integer value from 1 to the maximum limit possible for your service.

3. Create or update the service using the following command:

   gcloud run services replace service.yaml

To view the current service-level maximum instances settings for your Cloud Run service:

1. In the Google Cloud console, go to Cloud Run:

   Go to Cloud Run

2. Click that service to open its Service details panel.

3. View the current setting in the upper right of the service details panel, next to Scaling.

1. Use the following command:

   gcloud run services describe SERVICE

2. Locate the value for Scaling: Auto (Min: MIN_VALUE, Max: MAX_VALUE) in the returned configuration.

Any configuration change leads to the creation of a new revision. Subsequent revisions will also automatically get this configuration setting unless you make explicit updates to change it.

By default, Cloud Run revisions are configured to scale up to a maximum of 100 instances.

You can change the maximum instances setting using the Google Cloud console, the Google Cloud CLI, or a YAML file when you create a new service or deploy a new revision.

1. In the Google Cloud console, go to Cloud Run:

   Go to Cloud Run

2. Find and click the service you want to update in the services list to open that service's details.

3. Click Edit and deploy new revision to display the revision deployment form.

4. Click the Container tab.

5. Locate the Revision scaling section. In the field labelled Maximum number of instances, specify the maximum number of container instances.

6. Click Deploy.

You can update the maximum number of instances of a given service by using the following command:

gcloud beta run services update SERVICE --max-instances MAX-VALUE

Replace the following:

• SERVICE: the name of your service.
• MAX-VALUE: the required maximum number of container instances, using any integer value from 1 to the maximum limit.

1. If you are creating a new service, skip this step. If you are updating an existing service, download its YAML configuration:

   gcloud run services describe SERVICE --format export > service.yaml

2. Update the autoscaling.knative.dev/maxScale: attribute:

   apiVersion: serving.knative.dev/v1
   kind: Service
   metadata:
     name: SERVICE
     annotations:
       run.googleapis.com/launch-stage: BETA
   spec:
     template:
       metadata:
         annotations:
           autoscaling.knative.dev/maxScale: 'MAX-INSTANCE'
         name: REVISION

   Replace the following:

   • SERVICE: the name of your Cloud Run service
   • MAX-INSTANCE: the required maximum number of container instances, using any integer value from 1 to the maximum limit.
   • REVISION with a new revision name or delete it (if present). If you supply a new revision name, it must meet the following criteria:
     • Starts with SERVICE-
     • Contains only lowercase letters, numbers and -
     • Does not end with a -
     • Does not exceed 63 characters

3. Create or update the service using the following command:

   gcloud run services replace service.yaml

To view the current revision-level maximum instances settings for your Cloud Run service:

1. In the Google Cloud console, go to Cloud Run:

   Go to Cloud Run

2. Click that service to open its Service details panel.

3. Click the Revisions tab.

4. In the details panel at the right, view the Revision max. instances setting listed under the Container tab.

1. Use the following command:

   gcloud run services describe SERVICE

2. Locate the value for Max instances: in the returned configuration.

The following table shows the behavior if you combine service-level maximum instances with revision-level minimum or maximum instances:

If you use traffic splitting, the service-level maximum instances are distributed across the revisions based on the proportion of the traffic split. For example, if the service-level maximum instances = 100, a 50/50 traffic split allocates 50 service-level maximum instances to each revision. The following table shows a sample configuration scenario:

• Traffic spit for Revision A: 10%
• Traffic split for Revision B: 10%
• Traffic split for Revision C : 80%

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4