traffic splitting

Related topics

• Google Cloud CLI configures traffic splitting From the official documentation: “After installing the [Google Cloud CLI](/sdk/docs), you run the following command to split traffic across multiple versions, for example:”
• HTTPRoute configures traffic splitting From the official documentation: “HTTPRoute resources let you configure weights on a list of Services. The relative weights between Services define the split of traffic between them. This is useful for splitting traffic during rollouts, canarying changes, or for emergencies.”
• traffic splitting is part of App Engine From the official documentation: “If the tasks are created by an App Engine app, you can take advantage of App Engine traffic splitting ([Standard](/appengine/docs/standard/java/splitting-traffic)/[Flex](/appengine/docs/flexible/java/splitting-traffic)) to smooth traffic increases.”
• traffic splitting is part of Cloud Run From the official documentation: “Cloud Run lets you specify which revisions should receive traffic and to specify traffic percentages that are received by a revision. This feature lets you rollback to a previous revision, gradually deploy a revision, and split traffic between multiple revisions.”
• traffic splitting is part of Traffic Director From the official documentation: “This document provides instructions for configuring Cloud Service Mesh with the following traffic management features: - Route matching - Traffic splitting”
• Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Traffic Director is part of Cloud Service Mesh From the official documentation: “`TRAFFIC_DIRECTOR`: The core infrastructure of Google Cloud serves as the Cloud Service Mesh control plane.”
• Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Cloud Logging works with Cloud Service Mesh From the official documentation: “Cloud Service Mesh integrates with Cloud Logging and Cloud Monitoring.”
• Cloud Run works with Cloud Service Mesh From the official documentation: “This section shows you how to troubleshoot common errors with Cloud Service Mesh and Cloud Run.”
• Cloud Storage works with Google Cloud CLI From the official documentation: “The gcloud CLI is the preferred command line tool for accessing Cloud Storage.”
• App Engine is an alternative to Cloud Run From the official documentation: “App Engine and Cloud Run are Google Cloud platforms for hosting apps and services.”
• Cloud Load Balancing works with Cloud Service Mesh From the official documentation: “Cloud Service Mesh works with Cloud Load Balancing to provide a managed ingress experience.”
• Google Cloud CLI configures Application Default Credentials From the official documentation: “To configure ADC with a user account, you use the Google Cloud CLI:”
• Identity-Aware Proxy secures App Engine From the official documentation: “Securing App Engine apps Enable IAP for App Engine apps.”
• Identity-Aware Proxy secures Cloud Run From the official documentation: “IAP provides a central authorization layer for HTTPS applications deployed to Cloud Run.”
• Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
• Cloud Service Mesh works with Identity-Aware Proxy From the official documentation: “Integrate Identity-Aware Proxy with Cloud Service Mesh”
• Cloud Service Mesh works with Traffic Director From the official documentation: “**Note:** This is only applicable to Cloud Service Mesh with Traffic Director implementation.”
• Application Default Credentials works with Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Cloud Run works with Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
• Cloud Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• App Engine works with Cloud Logging From the official documentation: “App Engine automatically sends both the request logs and app logs to the [Cloud Logging](/logging/docs/overview) agent.”
• App Engine works with Cloud Storage From the official documentation: “To use a Cloud Storage bucket from an App Engine app:”
• App Engine works with Identity-Aware Proxy From the official documentation: “Validate a JWT passed to your App Engine app by Identity-Aware Proxy.”
• Application Default Credentials configures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see [Set up authentication for client libraries](/storage/docs/authentication#client-libs).”
• Application Default Credentials works with Google Cloud CLI From the official documentation: “To do so, provide your user credentials to ADC by using the Google Cloud CLI.”
• Cloud Load Balancing works with Cloud Run From the official documentation: “If you are using Cloud Load Balancing with Cloud Run, configure custom error responses at the load balancer level.”
• Cloud Logging depends on Application Default Credentials From the official documentation: “To authenticate to Logging, set up Application Default Credentials.”
• Cloud Logging is an alternative to Cloud Storage From the official documentation: “Instead, they are routed to either Cloud Storage (recommended) or Cloud Logging, depending on your organization's configuration.”
• Cloud Logging works with Traffic Director From the official documentation: “Cloud Service Mesh supports MeshConfig telemetry API to enable and disable Cloud Logging and Cloud Monitoring for GKE workloads.”
• 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 Traffic Director From the official documentation: “This page provides a reference for the APIs that are used to configure Cloud Service Mesh for Cloud Run workloads.”
• Google Cloud CLI depends on Application Default Credentials From the official documentation: “To authenticate with the gcloud CLI, generate a local Application Default Credentials (ADC) file by running this command.”
• App Engine works with Application Default Credentials From the official documentation: “The Application Default Credentials (ADC) infer authentication details for App Engine apps.”
• App Engine works with Cloud Load Balancing From the official documentation: “If you want to use an IP address that only maps to your domain then you should instead [set up a load balancer with App Engine](/load-balancing/docs/https/setting-up-https-serverless).”
• App Engine depends on Cloud Storage From the official documentation: “App Engine creates a [default Cloud Storage multi-regional bucket](/appengine/docs/flexible/locations#cloud-storage-location) on your behalf on the same region where it creates your application. It requires this bucket to store the contents of your application.”
• App Engine is an alternative to Cloud Storage From the official documentation: “You can use durable storage like Cloud Storage or an in-memory cache like App Engine to share data between pipeline instances.”
• 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 is an alternative to Google Cloud CLI From the official documentation: “You can authenticate to [the Vision API](/vision/docs/reference/rest) by using your [gcloud CLI credentials](/sdk/docs/authenticate) or by using [Application Default Credentials](/docs/authentication/application-default-credentials).”
• Cloud Load Balancing is an alternative to Cloud Service Mesh From the official documentation: “If you want to use [Cloud Load Balancing, Ingress, or Cloud Service Mesh to handle the SSL configuration](/migrate/containers/docs/windows/prepare-windows-cluster#secure-access), then you need to set `protocol` to `http`:”
• Cloud Load Balancing works with Identity-Aware Proxy From the official documentation: “IAP also supports and seamlessly integrates with Cloud Load Balancing, making it the most efficient security management option for this tutorial.”
• Cloud Load Balancing works with Traffic Director From the official documentation: “This section configures Cloud Service Mesh using Compute Engine load balancing resources.”
• Cloud Logging works with Cloud Run From the official documentation: “Cloud Logging captures, stores, and analyzes Cloud Run logs.”
• Cloud Logging is an alternative to Google Cloud CLI From the official documentation: “This section shows you how to verify the encryption key that was used during cluster creation. You can perform this verification using Cloud Logging or by using the Google Cloud CLI.”
• Cloud Run works with Google Cloud CLI From the official documentation: “Google Cloud CLI contains a [local development environment](/sdk/gcloud/reference/beta/code/dev) for emulating Cloud Run that can build a container from source, run the container on your local machine, and automatically rebuild the container upon source code changes.”
• Cloud Run works with Identity-Aware Proxy From the official documentation: “Enable IAP on the Cloud Run service.”
• Cloud Service Mesh works with HTTPRoute From the official documentation: “Configuring Envoy sidecar proxy configuration with HTTP services with regional HTTPRoute and regional Cloud Service Mesh”
• Cloud Service Mesh depends on Traffic Director From the official documentation: “This feature is only available to managed Cloud Service Mesh users using Traffic Director as control plane and requires data plane version 1.19.10-asm.22 or later.”
• Google Cloud CLI configures Cloud Logging From the official documentation: “You can update your cluster's [Cloud Logging](/kubernetes-engine/multi-cloud/docs/aws/how-to/cloud-logging) configuration settings with the Google Cloud CLI.”
• Google Cloud CLI works with Identity-Aware Proxy From the official documentation: “From the primary database, copy the password file to the standby database using Identity-Aware Proxy (IAP) and Google Cloud CLI command `gcloud compute scp`.”
• Google Cloud CLI configures Traffic Director From the official documentation: “To configure Google Cloud's managed load-balancing products and Cloud Service Mesh, you can use the Google Cloud CLI and Compute Engine APIs.”
• HTTPRoute configures Cloud Load Balancing From the official documentation: “When you deploy the `HTTPRoute` resource it creates an external Layer 7 Cloud Load Balancing resource and exposes the frontend `ServiceImport` backed by the frontend services that run in the *std-west*, *auto-east*, and *auto-central* clusters.”
• Identity-Aware Proxy secures Cloud Service Mesh From the official documentation: “The IAP integration with Cloud Service Mesh enables you to safely access services based on Google's [BeyondCorp principles](/beyondcorp).”
• Identity-Aware Proxy works with Traffic Director From the official documentation: “You authenticate users who are accessing any service exposed on a Cloud Service Mesh ingress gateway by using [Identity-Aware Proxy (IAP)](/iap).”