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.”
• ServiceImports works with traffic splitting From the official documentation: “ServiceImports represent multi-cluster Services and enable traffic splitting between different Services on different clusters.”
• session affinity works with traffic splitting From the official documentation: “If you are splitting traffic between multiple revisions with session affinity enabled, see [Session affinity and traffic splitting](/run/docs/configuring/session-affinity#affinity-and-traffic-splitting) for details on the effect of session affinity on traffic splitting.”
• 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.”
• Artifact Registry works with Cloud Build From the official documentation: “1. Builds your container and pushes it to Artifact Registry.”
• Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Cloud Build works with Cloud Storage From the official documentation: “Cloud Build then stores Terraform files and the Terraform State File in a Cloud Storage bucket.”
• 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.”
• Artifact Registry works with Cloud Run From the official documentation: “Cloud Run recommends using Artifact Registry.”
• 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 Build works with Cloud Run From the official documentation: “Cloud Build - create container images and deploy to Cloud Run.”
• 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 Build From the official documentation: “Cloud Build builds your app and deploys it to App Engine.”
• 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.”
• Artifact Registry works with Google Cloud CLI From the official documentation: “Before you can push or pull images, configure Docker to use the Google Cloud CLI to authenticate requests to Artifact Registry.”
• 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 Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• 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 Artifact Registry From the official documentation: “App Engine stores built container images in [Artifact Registry](https://console.cloud.google.com/artifacts/).”
• App Engine depends on Cloud Build From the official documentation: “In addition, all App Engine runtimes now use Cloud Build to build apps into a container during the deployment process.”
• 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 Build From the official documentation: “To authenticate to Cloud Build, 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).”
• Artifact Registry secures Cloud Run From the official documentation: “You can use Artifact Registry together with other Google Cloud products and features to improve the security posture of developer workflows and tools, software dependencies, CI/CD systems used to build and deploy your software, and runtime environments such as Google Kubernetes…”
• Artifact Registry depends on Cloud Storage From the official documentation: “The registry service hosts your custom images in Cloud Storage under your Google Cloud project.”
• Artifact Registry works with Cloud Storage From the official documentation: “| Artifact Registry | Stored in Cloud Storage, for each data chunk | |”
• Cloud Build depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Build, set up Application Default Credentials.”
• Cloud Build depends on Cloud Storage From the official documentation: “Cloud Build uses Cloud Storage to store build resources.”
• Cloud Build works with Google Cloud CLI From the official documentation: “Use `gcloud` to submit the application source code to Cloud Build:”
• 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 Run depends on Artifact Registry From the official documentation: “The containerized function is stored in Artifact Registry and deployed to Cloud Run as a service.”
• 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.”
• 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`.”
• 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.”
• session affinity is part of App Engine From the official documentation: “To allow App Engine to send requests by the same user to the same instance, you can enable session affinity.”
• session affinity is part of Cloud Load Balancing From the official documentation: “You can take advantage of [session affinity](/compute/docs/load-balancing/http#session_affinity) in Cloud Load Balancing. This feature ensures that all requests from a single client are routed to the same app instance.”
• session affinity is part of Cloud Run From the official documentation: “Even if you use Cloud Run [session affinity](/run/docs/configuring/session-affinity), it is possible for new requests to be load balanced to active containers, which allows containers to scale in.”