failover

Related topics

• failover depends on high availability From the official documentation: “If high availability (HA) is available, trigger a failover.”
• automatic failover is part of failover From the official documentation: “The AlloyDB Omni Operator supports both automatic and manual failover. Automatic failover is enabled by default.”
• failover is part of global external Application Load Balancer From the official documentation: “To learn how to configure failover for global external Application Load Balancers, see [Failover for global external Application Load Balancers](/load-balancing/docs/https/global-applb-failover-overview).”
• Google Cloud CLI configures failover From the official documentation: “Use the [`gcloud spanner databases change-quorum`](/sdk/gcloud/reference/spanner/databases/change-quorum) command to change the dual-region quorum from dual-region to a single region.”
• Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
• Identity-Aware Proxy secures Cloud Run From the official documentation: “IAP provides a central authorization layer for HTTPS applications deployed to Cloud Run.”
• GKE works with Identity-Aware Proxy From the official documentation: “If you are running GKE version 1.24 or later, you can configure IAP and GKE by using the Kubernetes Gateway API.”
• Cloud Run is an alternative to GKE From the official documentation: “For your containerized websites, you can also deploy them to [Cloud Run](/run) in addition to [using GKE](#kubernetes-engine).”
• Google Cloud Armor secures global external Application Load Balancer From the official documentation: “Cloud Armor also provides configurable security policies to services accessed through an external Application Load Balancer.”
• Cloud Run works with GKE From the official documentation: “Leverage Google Kubernetes Engine (GKE) and Cloud Run to deploy applications to the Google Cloud, optimizing costs, performance, and management overhead.”
• Cloud Run works with global external Application Load Balancer From the official documentation: “You can use a global external Application Load Balancer as the frontend for your Cloud Run, Cloud Run functions, and App Engine applications.”
• Cloud Run works with regional external Application Load Balancer From the official documentation: “To control access to the application, [disable the default `run.app` URL](/run/docs/securing/ingress#disable-url) of the frontend Cloud Run service and [set up a regional external Application Load Balancer](/load-balancing/docs/https/setting-up-reg-ext-https-serverless).”
• GKE works with Google Cloud CLI From the official documentation: “GKE manages end-user authentication for you through the Google Cloud CLI.”
• Cloud Logging works with Cloud Run From the official documentation: “Cloud Logging captures, stores, and analyzes Cloud Run logs.”
• Cloud Logging works with global external Application Load Balancer From the official documentation: “This document shows you how to configure and use [Cloud Logging](/logging) and [Cloud Monitoring](/monitoring) with classic Application Load Balancers, global external Application Load Balancers, and Cloud CDN.”
• Cloud Logging works with Google Cloud Armor From the official documentation: “Each HTTP(S) request that is evaluated against a Cloud Armor security policy is logged through Cloud Logging.”
• 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 Logging works with regional external Application Load Balancer From the official documentation: “This document shows you how to configure and use [Cloud Logging](/logging) and [Cloud Monitoring](/monitoring) with regional external Application Load Balancers.”
• Cloud Run works with Google Cloud Armor From the official documentation: “See Google Cloud Armor documentation to learn how to [use Google Cloud Armor with Cloud Run](/armor/docs/integrating-cloud-armor#serverless).”
• 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.”
• GKE works with global external Application Load Balancer From the official documentation: “After you [create the equivalent resources](#migrate-resources), exposing external endpoints behind a global external Application Load Balancer enables you to gradually migrate traffic between Cloud Run and Google Kubernetes Engine (GKE).”
• GKE works with Google Cloud Armor From the official documentation: “This document explains how Cloud Armor interacts with VPC firewall rules, Identity-Aware Proxy (IAP), Google Kubernetes Engine (GKE), Cloud CDN, and Global Front End.”
• GKE configures Google Cloud Armor From the official documentation: “You can configure Cloud Armor by using Google Kubernetes Engine (GKE) ingress security policies.”
• global external Application Load Balancer works with Identity-Aware Proxy From the official documentation: “To enable IAP for the [Application Load Balancer for both the global external mode or the classic mode](/load-balancing/docs/application-load-balancer), you enable it on the backend services of the load balancer.”
• global external Application Load Balancer is an alternative to regional external Application Load Balancer From the official documentation: “To load-balance external traffic to an application that's distributed across multiple regions, you can use either a global load balancer or multiple regional load balancers.”
• Google Cloud Armor secures Cloud Run From the official documentation: “Google Cloud Armor helps you protect your Cloud Run services from multiple types of threats, including distributed denial-of-service (DDoS) attacks and application attacks like cross-site scripting (XSS) and SQL injection (SQLi).”
• Google Cloud Armor works with Identity-Aware Proxy From the official documentation: “This document explains how Cloud Armor interacts with VPC firewall rules, Identity-Aware Proxy (IAP), Google Kubernetes Engine (GKE), Cloud CDN, and Global Front End.”
• 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 configures Google Cloud Armor From the official documentation: “This page lists the API resources and Google Cloud CLI command groups that you use to configure Cloud Armor.”
• 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`.”
• high availability is part of regional external Application Load Balancer From the official documentation: “To learn how to configure high availability for regional external Application Load Balancers, see [High availability for regional external Application Load Balancers](/load-balancing/docs/https/reg-applb-ha-overview).”
• Identity-Aware Proxy secures GKE From the official documentation: “Securing Google Kubernetes Engine apps Enable IAP for GKE apps.”