Envoy proxy

Related topics

• Cloud Service Mesh configures Envoy proxy From the official documentation: “Cloud Service Mesh configures the Envoy proxy to do the following:”
• Envoy proxy is part of Cloud Service Mesh From the official documentation: “Cloud Service Mesh works by placing an [Envoy](https://www.envoyproxy.io) sidecar proxy in each Pod.”
• Envoy proxy depends on Cloud Service Mesh From the official documentation: “Envoy proxies running as sidecars receive their service routing configuration from Cloud Service Mesh.”
• Cloud Service Mesh works with Envoy proxy From the official documentation: “Create a VM with an Envoy proxy that is connected to Cloud Service Mesh.”
• Cloud Trace works with Envoy proxy From the official documentation: “Generates a trace entry and sends it to Trace by using OpenCensus Envoy tracing.”
• Envoy proxy depends on Cloud Monitoring API From the official documentation: “For metrics, the sidecar proxies call the Cloud Monitoring API approximately every minute.”
• Envoy proxy works with global external Application Load Balancer From the official documentation: “**Global external Application Load Balancer**. This is a global load balancer that is implemented as a managed service on [Google Front Ends (GFEs)](/docs/security/infrastructure/design#google-frontend-service). It uses the open-source [Envoy proxy](https://www.envoyproxy.io/)…”
• Envoy proxy works with Google Cloud Observability From the official documentation: “In Cloud Service Mesh telemetry, the Envoy proxies call the Google Cloud Observability APIs periodically to report telemetry data.”
• Envoy proxy is an alternative to Google Front Ends From the official documentation: “Some Google Cloud load balancers use [Google Front Ends (GFEs)](https://cloud.google.com/security/infrastructure/design#google_front_end_service) as the client to the backends whereas others use the open source [Envoy proxy](https://www.envoyproxy.io/).”
• Envoy proxy works with HTTPRoute From the official documentation: “Envoy sidecar deployments support all Routes (`HTTPRoute`, `GRPCRoute`, `TCPRoute`, and `TLSRoute`).”
• Envoy proxy works with instance template From the official documentation: “Create an instance template for a VM running an automatically deployed Envoy service proxy.”
• Envoy proxy works with regional external Application Load Balancer From the official documentation: “**Regional external Application Load Balancer**. This is a regional load balancer that is implemented as a managed service on the open-source [Envoy proxy](https://www.envoyproxy.io/).”
• Envoy proxy depends on Workload Identity Federation for GKE From the official documentation: “When Envoy (`envoy-proxy`) connects to Cloud Service Mesh to fetch the xDS configuration, it uses Workload Identity Federation for GKE and the Pod's Kubernetes ServiceAccount.”
• HTTPRoute depends on Envoy proxy From the official documentation: “`HTTPRoute`, which is available only in meshes using Envoy proxies.”
• HTTPRoute configures Envoy proxy From the official documentation: “When you use the `HTTPRoute` resource to configure the Envoy proxies to send HTTP requests, all the capabilities in this document are available.”
• 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.”
• Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
• Cloud Monitoring works with Cloud Service Mesh From the official documentation: “Cloud Service Mesh integrates with Cloud Logging and Cloud Monitoring.”
• Cloud Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
• Cloud Service Mesh works with Cloud Trace From the official documentation: “Integrate with Cloud Trace, which is an optional feature in Cloud Service Mesh.”
• Cloud Service Mesh works with GKE From the official documentation: “# Set up a proxyless gRPC service mesh on GKE”
• 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 Service Mesh depends on GKE From the official documentation: “Provision managed Cloud Service Mesh on a GKE cluster.”
• Cloud Logging works with Cloud Monitoring From the official documentation: “You can store and view query-response activity logs in Cloud Logging and set up logs-based monitoring by using Cloud Monitoring.”
• Cloud Service Mesh works with Traffic Director From the official documentation: “**Note:** This is only applicable to Cloud Service Mesh with Traffic Director implementation.”
• GKE works with Traffic Director From the official documentation: “Provision managed Cloud Service Mesh on a GKE cluster.”
• GKE works with Workload Identity Federation for GKE From the official documentation: “Workload Identity Federation for GKE (for workloads running on Google Kubernetes Engine only)”
• 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).”
• Cloud Run works with Identity and Access Management From the official documentation: “For example, a remote backend deployed on Cloud Run can use Identity and Access Management (IAM) to:”
• Cloud Service Mesh depends on Cloud Monitoring From the official documentation: “Cloud Service Mesh uses Cloud Monitoring to provide automatic telemetry and logs.”
• Identity and Access Management works with Workload Identity Federation for GKE From the official documentation: “Instead, your GKE cluster directly authenticates workloads using Google Cloud IAM.”
• Workload Identity Federation for GKE is part of GKE From the official documentation: “Enable Workload Identity Federation for GKE:”
• Cloud Logging works with Cloud Trace From the official documentation: “To identify requests with high latency using Cloud Logging, apply the `traceSampled=true` filter to correlate logs in Cloud Logging with traces in Cloud Trace.”
• 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 Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
• Cloud Monitoring 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 Monitoring API is part of Cloud Monitoring From the official documentation: “The Cloud Monitoring API, client libraries, metric and resource type references, and MCP tools let you programmatically access and manage Cloud Monitoring.”
• 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 Google Cloud Observability From the official documentation: “Cloud Run automatically uses Google Cloud Observability to aggregate and review your logs, as described in the [logging page](/run/docs/logging).”
• 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).”
• 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.”
• Cloud Service Mesh depends on Google Cloud Observability From the official documentation: “If you want to use Cloud Service Mesh dashboards, you must enable Stackdriver.”
• Cloud Service Mesh works with Workload Identity Federation for GKE From the official documentation: “When Envoy (`envoy-proxy`) connects to Cloud Service Mesh to fetch the xDS configuration, it uses Workload Identity Federation for GKE and the Compute Engine VM default service account (unless the bootstrap was changed).”
• Cloud Trace is part of Cloud Service Mesh From the official documentation: “Integrate with Cloud Trace, which is an optional feature in Cloud Service Mesh.”
• Cloud Trace works with Traffic Director From the official documentation: “Integrate with Cloud Trace, which is an optional feature in Cloud Service Mesh.”
• Workload Identity Federation for GKE depends on GKE From the official documentation: “Workload Identity Federation for GKE provides a highly secure and automated authentication mechanism, simplifying key management. This method is specific to GKE clusters.”
• Cloud Logging is an alternative to Cloud Monitoring From the official documentation: “To see the status of your invalidation request or find a definitive list of recently submitted requests, you can use Cloud Logging or Cloud Monitoring.”
• 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 Cloud Trace From the official documentation: “You can use Cloud Trace or Cloud Logging to understand how long a particular request has taken.”
• 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 is part of Google Cloud Observability From the official documentation: “Logging is enabled by default, and belongs to Google Cloud Observability.”
• 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 Monitoring works with global external Application Load Balancer From the official documentation: “The load balancer also exports monitoring data to Cloud Monitoring.”
• Cloud Monitoring is part of Google Cloud Observability From the official documentation: “PHP libraries are available for the following Stackdriver services: - [Error Reporting](#error_reporting) - [Cloud Logging](#logging) - [Cloud Monitoring](#monitoring)”
• Cloud Monitoring works with Google Cloud Observability From the official documentation: “To develop effective alerting and monitoring dashboards and mechanisms, use [Google Cloud Observability](/stackdriver/docs) tools together with [Cloud Monitoring](/monitoring/docs/monitoring-overview).”
• Cloud Monitoring 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 Service Mesh works with Google Cloud Observability From the official documentation: “In Cloud Service Mesh telemetry, the Envoy proxies call the Google Cloud Observability APIs periodically to report telemetry data.”
• 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”