Deploy, operate, and secure workloads on Google Cloud, from projects and billing to IAM, and track your readiness for the Associate Cloud Engineer exam Domain by Domain.
Points to what builds on itWorks with or alternative toHover or tap a line to see what connects the two
Connect gateway works with Google Groups From the official documentation: “For kubectl access using connect gateway, you need to grant IAM roles to Google groups:”
GKE works with Google Groups From the official documentation: “Ensure Google Kubernetes Engine RBAC/cluster access is managed via Google Groups.”
Google Groups configures Connect gateway From the official documentation: “If you use Google Groups to manage access to the connect gateway, the gateway includes user group information in the request header.”
Google Groups works with IAM From the official documentation: “Use Google Groups to efficiently assign and manage IAM for users.”
Google Groups is part of IAM policy binding From the official documentation: “If true, the identities section of the result will expand any Google groups appearing in an IAM policy binding.”
Google Groups works with Kubernetes RBAC From the official documentation: “Set up Google Groups to work with Kubernetes role-based access control (RBAC) in your GKE clusters.”
Application Default Credentials secures BigQuery
BigQuery depends on Application Default Credentials
Application Default Credentials works with BigQuery
Identity and Access Management works with Kubernetes RBAC
Application Default Credentials secures IAM
Cloud Build works with Connect gateway
Connect gateway is an alternative to Kubernetes RBAC
GKE works with Identity-Aware Proxy
GKE works with Workload Identity Federation for GKE