autoscaler

Related topics

• autoscaler is part of Compute Engine From the official documentation: “This example assumes you are familiar with Docker containers, as well as Compute Engine resources, particularly HTTP load balancing, autoscaling, managed instance groups, and instance templates.”
• autoscaler is part of managed instance group From the official documentation: “Although autoscaling is a feature of managed instance groups, it is a separate API resource.”
• autoscaler configures managed instance group From the official documentation: “An autoscaler handles multiple signals by calculating the recommended number of VMs for each signal and then picking the signal that results in the largest number of VMs in the MIG.”
• autoscaler is part of managed instance groups From the official documentation: “Autoscaling is a feature of [managed instance groups](/compute/docs/instance-groups).”
• autoscaler works with managed instance group From the official documentation: “If you delete a MIG using the gcloud CLI, any autoscalers attached to the MIG are also deleted.”
• autoscaler works with Pub/Sub From the official documentation: “To configure autoscaling based on unacknowledged messages in a [Pub/Sub](/pubsub/docs) subscription, use the `subscription/num_undelivered_messages` metric provided by [`pubsub`](/monitoring/api/metrics_gcp_p_z#gcp-pubsub) and filter by the `subscription ID`.”
• gcloud CLI configures autoscaler From the official documentation: “When you delete a managed instance group and its instances by using the [Google Cloud console](https://console.cloud.google.com/) or the [gcloud CLI](/compute/docs/gcloud-compute), any attached autoscaler is automatically deleted.”
• predictive autoscaling is part of autoscaler From the official documentation: “With predictive autoscaling enabled, the autoscaler works with real-time data as well as with historical data to cover both the current and forecasted load.”
• scale-in controls is part of autoscaler From the official documentation: “Configure scale-in controls by setting the `maxScaledInReplicas` and `timeWindowSec` fields within the `autoscalingPolicy.scaleInControl` structure in a [zonal](/compute/docs/reference/rest/v1/autoscalers) or [regional](/compute/docs/reference/rest/v1/regionAutoscalers)…”
• scale-in controls configures autoscaler From the official documentation: “Update scale-in controls in a MIG's existing autoscaler by using the `--scale-in-control` flag with the [`gcloud compute instance-groups managed update-autoscaling` command](/sdk/gcloud/reference/compute/instance-groups/managed/update-autoscaling).”
• backend service works with managed instance group From the official documentation: “Add the backend instance group to the backend service.”
• Cloud Run depends on Pub/Sub From the official documentation: “Cloud Run function triggered by Pub/Sub to fetch HYPR MFA logs and write to GCS.”
• Application Default Credentials works with Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Application Default Credentials secures Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• managed instance group is part of backend service From the official documentation: “Add the managed instance group to the backend service.”
• Pub/Sub depends on Application Default Credentials From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Application Default Credentials works with Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• instance template configures managed instance group From the official documentation: “Create the MIG using the template.”
• managed instance group depends on instance template From the official documentation: “All MIGs require an instance template.”
• Application Default Credentials secures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• Cloud Logging works with Pub/Sub From the official documentation: “Pub/Sub writes various log entries to Cloud Logging in the Google Cloud console.”
• autoscaling is part of managed instance groups From the official documentation: “Although autoscaling is a feature of MIGs, it is a separate REST resource.”
• backend service works with managed instance groups From the official documentation: “Add the managed instance group to the backend service.”
• instance template works with managed instance group From the official documentation: “Create a global instance template that you can use to create a managed instance group (MIG) of GPU VMs.”
• Application Default Credentials works with Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
• instance template is part of Compute Engine From the official documentation: “An instance template is an immutable Compute Engine resource that stores VM configuration.”
• managed instance groups is part of backend service From the official documentation: “Add the managed instance group to the backend service.”
• autoscaling is part of managed instance group From the official documentation: “Create a MIG with autoscaling enabled”
• backend service depends on managed instance group From the official documentation: “As a part of this step, you need to assign the health check that you created to the backend service and add the instance group as the backend to the backend service.”
• Cloud Logging depends on Application Default Credentials From the official documentation: “To authenticate to Logging, set up Application Default Credentials.”
• Cloud Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Cloud Run works with Pub/Sub From the official documentation: “A Cloud Run app receives the Pub/Sub message.”
• gcloud CLI configures Application Default Credentials From the official documentation: “**gcloud CLI**: Manage cloud resources, configure projects, and set up local Application Default Credentials (ADC).”
• managed instance group is part of Compute Engine From the official documentation: “Checks if a Compute Engine Managed Instance Group (MIG) is configured as Zonal.”
• managed instance groups is part of Compute Engine From the official documentation: “Compute Engine provides a straightforward way to implement autoscaling through managed instance groups.”
• managed instance groups depends on instance template From the official documentation: “Create multiple regional managed instance groups using the instance template.”
• Application Default Credentials works with Cloud Logging From the official documentation: “To authenticate to Logging, set up Application Default Credentials.”
• Application Default Credentials configures Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Application Default Credentials configures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• autoscaling is part of Cloud Run From the official documentation: “When using autoscaling, each Cloud Run revision is automatically scaled to the number of instances needed to handle all incoming requests, events, or CPU utilization.”
• autoscaling is part of Compute Engine From the official documentation: “Compute Engine: [Autoscaling](/compute/docs/autoscaler), [custom machine types](/compute/docs/instances/creating-instance-with-custom-machine-type), and [Spot VMs](/compute/docs/instances/spot)”
• autoscaling works with managed instance group From the official documentation: “Use Terraform to create a regional managed instance group (MIG) with autoscaling enabled.”
• backend service works with Cloud Logging From the official documentation: “After you enable logging on the backend service, HTTP or HTTPS requests are logged by using [Cloud Logging](/logging/docs) logs requests.”
• backend service works with Pub/Sub From the official documentation: “This lab concentrates on the backend service, putting together Pub/Sub, Natural Language, and Spanner services and APIs to collect and analyze feedback and scores from an online Quiz application.”
• Cloud Logging works with Cloud Run From the official documentation: “Cloud Logging captures, stores, and analyzes Cloud Run logs.”
• Cloud Logging works with gcloud CLI From the official documentation: “To read log entries in Logging, you can do any of the following: - In the Google Cloud console, go to the segment **Logs Explorer** page: [Go to **Logs Explorer**](https://console.cloud.google.com/logs/query) If you use the search bar to find this page, then select the result…”
• Cloud Run works with Compute Engine From the official documentation: “This lets Cloud Run clients use this backend service route to send requests directly to Compute Engine instances.”
• Cloud Run works with gcloud CLI From the official documentation: “This command obtains a service account key from an environment variable and then uses the gcloud CLI to deploy the application to Cloud Run.”
• gcloud CLI works with Pub/Sub From the official documentation: “Download and install the [Google Cloud CLI](/sdk/docs/install) to use the gcloud CLI with the Pub/Sub API if you have not installed it previously.”
• instance template is part of managed instance group From the official documentation: “Each VM in a MIG is based on an instance template.”
• instance template configures managed instance groups From the official documentation: “Using the instance template, configure a [managed instance group](/compute/docs/instance-groups/creating-groups-of-managed-instances) with a target size of 1.”
• managed instance group is part of managed instance groups From the official documentation: “You can build highly available deployments of stateful workloads on VMs using stateful managed instance groups (stateful MIGs).”
• scale-in controls configures autoscaling From the official documentation: “Configure scale-in controls to prevent the autoscaler from prematurely scaling down the group during downtime when traffic is switching over from the global load balancer to the regional load balancer.”