Connect gateway

Related topics

• Cloud Build works with Connect gateway From the official documentation: “Learn how to [access Anthos clusters from Cloud Build with the connect gateway](/../anthos/multicluster-management/gateway/tutorials/cloud-build-integration).”
• Connect gateway depends on fleet From the official documentation: “Only clusters registered to your project fleet can be accessed through the Connect gateway.”
• Connect gateway depends on Connect Agent From the official documentation: “You need at least one node pool to use Connect gateway because it relies on the Connect agent, which runs as a Deployment in the cluster.”
• Connect gateway depends on Fleets From the official documentation: “The Connect gateway builds on the power of fleets to let users connect to and run commands against registered clusters in a consistent and secure way.”
• Connect gateway works with Google Distributed Cloud connected From the official documentation: “`connectgateway.googleapis.com`: provides a secure connection between the Config Delivery service and your Distributed Cloud connected clusters”
• Connect gateway works with Identity and Access Management From the official documentation: “Google recommends that you use [Connect gateway](/distributed-cloud/connected/latest/docs/clusters#gateway) as the primary access method to leverage Identity and Access Management.”
• Connect gateway depends on node pool From the official documentation: “You need at least one node pool to use Connect gateway because it relies on the Connect agent, which runs as a Deployment in the cluster.”
• Connect gateway works with service account impersonation From the official documentation: “The Connect gateway supports [service account impersonation](/iam/docs/service-account-impersonation), so even if you're logged in to your own user account you can use a service account to interact with clusters, as you'll see in the following sections.”
• VPC Service Controls secures Connect gateway From the official documentation: “You can use VPC Service Controls with the Connect gateway for extra data security, once you ensure that the necessary APIs to use the gateway can be accessed from within your specified service perimeter.”
• Cloud Service Mesh depends on fleet From the official documentation: “All clusters in a particular Cloud Service Mesh must be registered to the same fleet.”
• Cloud Service Mesh works with GKE From the official documentation: “# Set up a proxyless gRPC service mesh on GKE”
• 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 Service Mesh works with VPC Service Controls From the official documentation: “You can now use VPC Service Controls with Cloud Service Mesh.”
• Cloud Key Management Service works with Google Distributed Cloud connected From the official documentation: “Distributed Cloud connected integrates with Cloud KMS by using the [envelope encryption model](/kms/docs/envelope-encryption).”
• Cloud Service Mesh depends on GKE From the official documentation: “Provision managed Cloud Service Mesh on a GKE cluster.”
• VPC Service Controls secures Cloud Service Mesh From the official documentation: “[VPC and VPC Service Controls](/vpc-service-controls) protect the mesh edge through the private network access controls.”
• Cloud Build works with Secret Manager From the official documentation: “The secret is configured to be accessible by Cloud Run and Cloud Build.”
• fleet works with GKE From the official documentation: “Created a GKE cluster and registered it to a fleet”
• fleet works with Google Distributed Cloud connected From the official documentation: “Distributed Cloud connected clusters are automatically registered to a Fleet in the project that they're created in.”
• GKE works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or GKE, the underlying instance or node must have the `cloud-platform` OAuth scope.”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
• Cloud Build works with GKE From the official documentation: “Remove the permission granted to Cloud Build to connect to GKE.”
• Cloud Build depends on Secret Manager From the official documentation: “Previously, for GitLab Enterprise and Bitbucket Data Center connections, when Secret Manager secrets were retrieved, permissions were checked against the Cloud Build service agent (P4SA) credentials only.”
• Cloud Service Mesh is part of fleet From the official documentation: “You can enable features such as Config Management and Cloud Service Mesh within your Fleet.”
• Cloud Service Mesh works with Google Kubernetes Engine From the official documentation: “A GKE Cluster with Cloud Service Mesh enabled”
• Google Kubernetes Engine works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or Google Kubernetes Engine, the underlying instance or node must have the `cloud-platform` OAuth scope.”
• Identity and Access Management secures Secret Manager From the official documentation: “Secret Manager uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management works with VPC Service Controls From the official documentation: “VPC Service Controls perimeters and Identity and Access Management (IAM) roles work together.”
• Cloud Build works with Cloud Key Management Service From the official documentation: “This page explains how to use encrypted information from Cloud KMS in Cloud Build.”
• Cloud Build depends on Cloud Storage From the official documentation: “Cloud Build uses Cloud Storage to store build resources.”
• Cloud Build depends on GKE From the official documentation: “To deploy the application in your Kubernetes cluster, Cloud Build needs the Kubernetes Engine Developer [Identity and Access Management Role](/iam/docs/understanding-roles).”
• Cloud Build works with Google Kubernetes Engine From the official documentation: “This tutorial shows you how to validate configs with [Cloud Build](/build) when using Google Kubernetes Engine clusters.”
• Cloud Key Management Service depends on Identity and Access Management From the official documentation: “Whatever the mechanism, Cloud KMS resolves the provided credential to identify the principal (the entity which is authenticated and is authorizing the request), and calls IAM to see whether the principal is authorized to make the request and whether an audit log is written.”
• Cloud Key Management Service works with Identity and Access Management From the official documentation: “The Cloud KMS platform is integrated with [IAM](/iam/docs/overview) and [Cloud Audit Logs](/logging/docs/audit) so that you can manage permissions on individual keys and audit how they are used.”
• Cloud Key Management Service works with Secret Manager From the official documentation: “If you want to control your encryption keys, then you can use customer-managed encryption keys (CMEKs) in [Cloud KMS](/kms/docs) with CMEK-integrated services including Secret Manager.”
• Cloud Key Management Service is an alternative to Secret Manager From the official documentation: “Secret Manager is the recommended technique for managing sensitive data with Cloud Build. For existing projects, you can continue using Cloud KMS, but for new projects, use Secret Manager.”
• Cloud Key Management Service works with VPC Service Controls From the official documentation: “If you want your Dataproc Metastore service to run inside a [VPC Service Controls](/dataproc-metastore/docs/vpc-sc) perimeter, you must add the Cloud Key Management Service (Cloud KMS) API to the perimeter.”
• Cloud Service Mesh depends on Fleets From the official documentation: “Cloud Service Mesh requires fleet membership for all control plane and setup options.”
• 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 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 Storage works with GKE From the official documentation: “This example configures GKE to store Pod snapshots in the `FOLDER_PATH/` path inside the Cloud Storage bucket `BUCKET_NAME`:”
• Cloud Storage works with Google Distributed Cloud connected From the official documentation: “- Manage Distributed Cloud connected data in Cloud Storage.”
• Cloud Storage works with Google Kubernetes Engine From the official documentation: “Often, media-related data residing in Cloud Storage is processed by applications running in Compute Engine or Google Kubernetes Engine, and the output of this process is written back to Cloud Storage.”
• 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).”
• fleet works with Google Kubernetes Engine From the official documentation: “- [Created a GKE cluster and registered it to a fleet](/service-mesh/v1.23/docs/gateway/prepare-gateway#create_and_register_a_cluster).”
• Fleets works with GKE From the official documentation: “If you are using [fleets](/kubernetes-engine/fleet-management/docs) with your Google Kubernetes Engine clusters, then you can enable continuous validation (CV) as a fleet-default configuration.”
• GKE works with Google Distributed Cloud connected From the official documentation: “A connected deployment of Distributed Cloud lets you run Google Kubernetes Engine (GKE) clusters on dedicated hardware provided and maintained by either Google or a Google-certified Systems Integrator (SI) that is installed directly on your premises and connects to your local…”
• GKE depends on Identity and Access Management From the official documentation: “GKE relies on and can be used with many other Google Cloud services, from IAM for access control to Cloud Billing for managing your costs.”
• Google Distributed Cloud connected works with Secret Manager From the official documentation: “- Manage Distributed Cloud connected credentials in Secret Manager.”
• Google Kubernetes Engine works with Identity and Access Management From the official documentation: “In GKE, you can also use IAM to manage which users and service accounts can access, and perform operations in, your clusters.”
• Identity and Access Management secures Cloud Build From the official documentation: “To grant other users access, you can grant Identity and Access Management (IAM) roles on the project, or on a specific Cloud Build resource.”
• Identity and Access Management secures Cloud Key Management Service From the official documentation: “If you need to prevent a user from using a Cloud KMS resource during the time needed for propagation of an eventually consistent operation, remove the Identity and Access Management (IAM) permission for the resource.”
• 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).”
• Identity and Access Management configures GKE From the official documentation: “First, as you would with most services on Google Cloud, you need to configure [IAM](/iam) roles in order to set up authorization on GKE.”
• node pool is part of GKE From the official documentation: “You create a cluster with [one node pool](/kubernetes-engine/docs/concepts/node-pools) (the default one).”
• node pool is part of Google Kubernetes Engine From the official documentation: “This document provides instructions on how to update the Kubernetes node labels and node taints of an existing node pool in a Google Kubernetes Engine (GKE) Standard cluster by using the GKE API.”
• VPC Service Controls secures Cloud Key Management Service From the official documentation: “After you configure VPC Service Controls, you restrict access to Cloud Key Management Service in VPC Service Controls or [enable domain restricted sharing](/resource-manager/docs/organization-policy/restricting-domains).”
• VPC Service Controls secures Secret Manager From the official documentation: “In addition to IAM controls, you can limit access to the Secret Manager API with network-based controls by setting up a [VPC Service Controls perimeter](/vpc-service-controls/docs/overview) for your organization.”