TLS

Related topics

• mTLS is an alternative to TLS From the official documentation: “Use TLS instead of mTLS”
• egress gateway works with TLS From the official documentation: “The egress gateway then terminates the mTLS connection and originates a regular TLS (HTTPS) connection to the destination host.”
• Authentication works with TLS From the official documentation: “Authentication and encryption that use transport layer security (TLS) and mutual TLS (mTLS) for both Cloud Service Mesh with Envoy and Cloud Service Mesh with proxyless gRPC applications.”
• TLS secures Cloud Run From the official documentation: “TLS is terminated by Cloud Run for HTTPS and gRPC, and then requests are proxied as HTTP/1 or gRPC to the container without TLS.”
• TLS secures identity provider From the official documentation: “To ensure authenticity, communication with your identity provider is secured by using TLS.”
• Cloud Service Mesh works with GKE From the official documentation: “# Set up a proxyless gRPC service mesh on GKE”
• 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.”
• Compute Engine is an alternative to GKE From the official documentation: “You can also deploy a third-party model to either Vertex AI Model Garden or self-host on GKE or Compute Engine.”
• Cloud Service Mesh depends on GKE From the official documentation: “Provision managed Cloud Service Mesh on a GKE cluster.”
• 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).”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• 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 Service Mesh works with Compute Engine From the official documentation: “Cloud Service Mesh supports a variety of infrastructures (GKE/Kubernetes, Compute Engine) and environments (on-premises, other clouds).”
• Authentication secures Compute Engine From the official documentation: “Authentication verifies your identity for access to Google Cloud services and APIs. To run code or samples from a local development environment, you can authenticate to Compute Engine by selecting one of the following options:”
• Authentication works with Vertex AI From the official documentation: “The Vertex AI models use the service account used to install AlloyDB Omni to authenticate, while other providers can use the Secret Manager or pass authentication details through headers.”
• Authentication configures Vertex AI From the official documentation: “For Vertex AI models, the AlloyDB service account is used for authentication.”
• 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 Vertex AI From the official documentation: “The Cloud Run service can interact with Vertex AI services.”
• Cloud Service Mesh works with identity provider From the official documentation: “You can integrate your existing Identity Provider with Cloud Service Mesh to provide browser-based end-user authentication and access control to your deployed workloads.”
• Cloud Service Mesh works with mTLS From the official documentation: “All Cloud Service Mesh services using mTLS are impacted by this CVE.”
• egress gateway is part of Cloud Service Mesh From the official documentation: “Cloud Service Mesh provides the [option to deploy](/service-mesh/v1.26/docs/operate-and-maintain/gateways) standalone forward-proxies, known as egress gateways, at the edge of the mesh.”
• egress gateway works with GKE From the official documentation: “This document describes how to use [Cloud Service Mesh](/service-mesh/v1.21/docs/overview) egress gateways and other Google Cloud controls to secure outbound traffic (egress) from workloads deployed on a Google Kubernetes Engine (GKE) cluster.”
• GKE is an alternative to Vertex AI From the official documentation: “Once you have your fine-tuned model, you can deploy it to a serving endpoint using Google Kubernetes Engine (GKE) or Vertex AI to make it accessible for inference.”
• mTLS is part of Cloud Service Mesh From the official documentation: “Cloud Service Mesh defends against MitM and data exfiltration attacks by enforcing [mTLS authentication and encryption](/service-mesh/v1.30/docs/security/security-overview#mutual_tls) for all communicating parties.”