Cloud Service Mesh

Related topics

• Certificate Authority Service works with Cloud Service Mesh From the official documentation: “Configure Cloud Service Mesh to use CA Service”
• Identity and Access Management secures Cloud Service Mesh From the official documentation: “Access to Cloud Service Mesh in the Google Cloud console is controlled by [Identity and Access Management (IAM)](/iam/docs/overview).”
• Cloud Service Mesh depends on Workload Identity Federation for GKE From the official documentation: “Cloud Service Mesh requires Workload Identity Federation for GKE and is the recommended way to access Google APIs from GKE workloads.”
• Mutual TLS is part of Cloud Service Mesh From the official documentation: “In Cloud Service Mesh, auto mTLS is enabled by default.”
• Cloud Logging works with Cloud Service Mesh From the official documentation: “Cloud Service Mesh stores the dry-run results to Cloud Logging in the following labels:”
• Cloud Monitoring works with Cloud Service Mesh From the official documentation: “Mesh telemetry is no longer automatically ingested into 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 works with VPC Service Controls From the official documentation: “You can now use VPC Service Controls with Cloud Service Mesh.”
• Cloud Service Mesh depends on Certificate Authority Service From the official documentation: “Cloud Service Mesh service security depends on the CA Service integration with GKE.”
• 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.”
• Cloud Service Mesh depends on GKE From the official documentation: “Provision managed Cloud Service Mesh on a GKE cluster.”
• Cloud Service Mesh works with GKE From the official documentation: “# Set up a proxyless gRPC service mesh on GKE”
• Cloud Service Mesh works with Google Kubernetes Engine From the official documentation: “A GKE Cluster with Cloud Service Mesh enabled”
• Cloud Service Mesh works with Identity-Aware Proxy From the official documentation: “Integrate Identity-Aware Proxy with Cloud Service Mesh”
• Cloud Service Mesh depends on Mutual TLS From the official documentation: “Cloud Service Mesh uses mutual TLS (mTLS) for peer authentication.”
• Cloud Service Mesh works with Compute Engine From the official documentation: “You can run applications on the following platforms and adopt them into a global service mesh that Cloud Service Mesh configures. | Feature | Supported | | --- | --- | | Compute Engine virtual machine (VM) instances | ✔ |”
• Cloud Service Mesh works with Identity and Access Management From the official documentation: “For information about how and which permissions are evaluated for each method, see the Identity and Access Management documentation for Cloud Service Mesh.”
• Cloud Service Mesh depends on Cloud Monitoring From the official documentation: “Cloud Service Mesh uses Cloud Monitoring to provide automatic telemetry and logs.”
• 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).”
• Mutual TLS secures Cloud Service Mesh From the official documentation: “mTLS is the means by which Cloud Service Mesh implements both *authentication* and *encryption* between services.”
• 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 Service Mesh depends on Google Kubernetes Engine From the official documentation: “Cloud Service Mesh service security is supported only with GKE.”
• Cloud Service Mesh works with Mutual TLS From the official documentation: “For workloads on GKE and Compute Engine, consider [Cloud Service Mesh](/service-mesh/docs/security/security-overview) so that you can use mTLS for mutual authentication (client and server) and encrypt communications in transit using certificates that you manage.”
• 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).”
• VPC Service Controls secures Cloud Service Mesh From the official documentation: “VPC Service Controls help defend against data exfiltration attacks and prevent external attackers from accessing services inside a mesh.”
• Cloud Storage works with Google SecOps From the official documentation: “Configure a feed in Google SecOps to ingest from Google Cloud Storage”
• Cloud Run works with Cloud SQL From the official documentation: “Learn how to connect to Cloud SQL from Cloud Run”
• Cloud SQL works with Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
• Cloud SQL works with Compute Engine From the official documentation: “Create a Compute Engine VM Instance to host a sample web app that connects to Cloud SQL.”
• Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
• Workload Identity Federation for GKE is part of GKE From the official documentation: “Enable Workload Identity Federation for GKE:”
• Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
• Compute Engine is an alternative to GKE From the official documentation: “To use TPU7x, you can use Google Kubernetes Engine (GKE) or Compute Engine.”
• Certificate Authority Service works with Certificate Manager From the official documentation: “To integrate CA Service with Certificate Manager, follow these steps:”
• Cloud Monitoring works with Cloud SQL From the official documentation: “You can also get more details by viewing the Cloud Monitoring logs for your Cloud SQL destination instance.”
• Cloud Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
• Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
• 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)”
• Identity-Aware Proxy secures Cloud Run From the official documentation: “There are two ways to enable Identity-Aware Proxy for your Cloud Run services.”
• Cloud Logging works with Cloud SQL From the official documentation: “Cloud SQL uses Cloud Logging.”
• Cloud Run is an alternative to GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
• Cloud SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
• Certificate Authority Service works with GKE From the official documentation: “Cloud Service Mesh service security depends on the CA Service integration with GKE.”
• Cloud Storage works with Identity and Access Management From the official documentation: “To learn how to use IAM with Cloud Storage, see [Using IAM Permissions](/storage/docs/access-control/using-iam-permissions).”
• 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.”
• Identity-Aware Proxy secures Compute Engine From the official documentation: “Securing Compute Engine apps Enable IAP for Compute Engine apps.”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
• Artifact Registry works with Cloud Run From the official documentation: “Cloud Run recommends using Artifact Registry.”
• Certificate Authority Service works with Cloud SQL From the official documentation: “Cloud SQL hosts and manages the root CA and subordinate server CAs on Google Cloud Certificate Authority Service (CA Service).”
• 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 SQL works with GKE From the official documentation: “[From an application running on GKE](/sql/docs/postgres/connect-kubernetes-engine)”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• Artifact Registry works with Compute Engine From the official documentation: “Compute Engine can pull containers directly from Artifact Registry repositories.”
• Artifact Registry works with GKE From the official documentation: “In the next tutorial, you deploy those images from the Artifact Registry repository to a GKE cluster:”
• Certificate Authority Service works with Cloud Storage From the official documentation: “For a Google-managed Cloud Storage bucket, CA Service creates a Google-managed bucket in the same location as the CA.”
• Certificate Manager works with Cloud Load Balancing From the official documentation: “Acquire and manage TLS (SSL) certificates for use with Cloud Load Balancing and Media CDN.”
• Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
• Cloud Run works with Identity-Aware Proxy From the official documentation: “On the Cloud Run security page, find the checkbox for Identity-Aware Proxy (IAP).”
• Cloud Storage works with Compute Engine From the official documentation: “You can use a web browser, the Google Cloud CLI, or a programming language to transfer files between Cloud Storage and Compute Engine VMs.”
• Compute Engine is an alternative to Google Kubernetes Engine From the official documentation: “You can install MongoDB on a Compute Engine instance or you can deploy MongoDB on Google Kubernetes Engine.”