workload identity federation

Related topics

• service account key is an alternative to workload identity federation From the official documentation: “For hosts outside of Google Cloud, you can provide a service account key or configure Workload Identity Federation (WIF).”
• service account keys is an alternative to workload identity federation From the official documentation: “Where possible, consider using Workload Identity Federation instead of service account keys.”
• GKE works with workload identity federation From the official documentation: “To allow GitHub Actions authenticate Google Cloud and deploy to GKE, use [workload identity federation](/iam/docs/workload-identity-federation).”
• gcloud CLI works with workload identity federation From the official documentation: “Support for Workload Identity Federation in gcloud CLI is available in [version 363.0.0 and later versions of the gcloud CLI](/sdk/docs/components#updating_components).”
• Application Default Credentials works with workload identity federation From the official documentation: “ADC also supports [Workload Identity Federation](#workload-identity-federation), enabling applications to access Google Cloud resources from external platforms like Amazon Web Services (AWS), Microsoft Azure, or any identity provider that supports OpenID Connect (OIDC).”
• Cloud Service Mesh depends on workload identity federation From the official documentation: “This error is shown if the GKE cluster does not have [Workload Identity Federation](/kubernetes-engine/docs/how-to/workload-identity) enabled on all node pools of that cluster, since this is a prerequisites for the installation of Cloud Service Mesh.”
• Security Token Service works with workload identity federation From the official documentation: “By using Workload Identity Federation, workloads that run on AWS EC2 and Azure VMs can exchange their environment-specific credentials for short-lived Google Cloud Security Token Service tokens.”
• workload identity federation depends on Security Token Service From the official documentation: “You provide a credential from your identity provider (IdP) to the [Security Token Service](/iam/docs/reference/sts/rest), which verifies the identity on the credential, and then returns a [federated access token](/docs/authentication/token-types#fed-access-tokens) in exchange.”
• workload identity federation depends on workload identity pool From the official documentation: “Using workload identity federation requires a workload identity pool and provider.”
• workload identity federation depends on workload identity pool provider From the official documentation: “Using workload identity federation requires a workload identity pool and provider.”
• access policy works with workload identity federation From the official documentation: “To create an IAM Access policy that allows an agent using Workload Identity Federation read-only access to a tool called `GitHubTool`, do the following:”
• Active Directory Federation Services works with workload identity federation From the official documentation: “By using Workload Identity Federation in combination with Active Directory Federation Services (AD FS), you can let these workloads exchange their Active Directory Kerberos credentials for short-lived Google Cloud credentials.”
• Cloud Run works with workload identity federation From the official documentation: “This tutorial describes how to use Workload Identity Federation to authenticate workloads that run outside of Google Cloud so that they can access microservices hosted by Cloud Run.”
• service account works with workload identity federation From the official documentation: “[configure Workload Identity Federation](/iam/docs/workload-identity-federation-with-other-clouds) to let applications running on-premises or on other cloud providers use a service account.”
• workload identity federation secures Cloud Run From the official documentation: “If your environment uses an identity provider supported by [workload identity federation](/iam/docs/workload-identity-federation), you can use the following method to securely authenticate to your Cloud Run service from outside Google Cloud:”
• workload identity federation is part of Identity and Access Management From the official documentation: “[Identity and Access Management (IAM)](/iam/docs/overview) lets you manage fine-grained access to services and resources in Google Cloud. IAM includes features such as the following: - [Privileged Access Manager](/iam/docs/pam-overview), which manages on-demand, temporary…”
• workload identity federation configures Pub/Sub From the official documentation: “If your architecture includes an [external identity provider](/iam/docs/workload-identity-federation#providers) such as Active Directory or a local Kubernetes cluster, you can use [workload identity federation](/iam/docs/workload-identity-federation) to manage access to Pub/Sub.”
• Workload Identity Federation for GKE is part of workload identity federation From the official documentation: “[Workload Identity Federation for GKE](/kubernetes-engine/docs/concepts/workload-identity) is a GKE-specific implementation of Workload Identity Federation that provides a project-wide Google-managed *workload identity pool* from which applications running in GKE clusters get…”
• workload identity pool is part of workload identity federation From the official documentation: “This procedure assumes you have already configured Workload Identity Federation for your Google Cloud project, including creating an Identity Pool and Provider, and granting appropriate IAM permissions to your Kubernetes service accounts.”
• workload identity pool depends on workload identity federation From the official documentation: “A workload identity pool is a set of workload identities that is managed by an external IdP and federated by using [Workload Identity Federation](/iam/docs/workload-identity-federation).”
• Application Default Credentials works with Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Application Default Credentials secures Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Pub/Sub depends on Application Default Credentials From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Cloud Run depends on service account From the official documentation: “The Cloud Run function needs a service account with permissions to write to GCS bucket and be invoked by Pub/Sub.”
• Application Default Credentials works with Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• Cloud Run works with Pub/Sub From the official documentation: “Route Cloud Pub/Sub events to Cloud Run”
• 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.”
• Workload Identity Federation for GKE is part of GKE From the official documentation: “Enable Workload Identity Federation for GKE:”
• Application Default Credentials secures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• Compute Engine is an alternative to GKE From the official documentation: “To use TPU7x, you can use Google Kubernetes Engine (GKE) or Compute Engine.”
• Compute Engine works with service account From the official documentation: “A common method is to attach a service account to a resource like a Compute Engine instance.”
• Cloud Monitoring depends on Application Default Credentials From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
• Cloud Monitoring works with Cloud Service Mesh From the official documentation: “Mesh telemetry is no longer automatically ingested into Cloud Monitoring.”
• Cloud Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
• 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 Run depends on Pub/Sub From the official documentation: “Create a Pub/Sub topic that Cloud Scheduler will publish to and the Cloud Run function will subscribe to.”
• 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)”
• workload identity pool provider is part of workload identity pool From the official documentation: “Add the cluster as a workload identity pool provider.”
• Cloud Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• 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.”
• service account key is an alternative to Workload Identity Federation for GKE From the official documentation: “Enabling it lets you use IAM policies to grant Kubernetes workloads in your GKE cluster access to specific Google Cloud APIs without needing manual configuration or less secure methods like service account key files.”
• 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.”
• Application Default Credentials works with Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Application Default Credentials works with Identity and Access Management From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
• 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”
• service account is part of Identity and Access Management From the official documentation: “Service accounts function as both principals and resources within IAM.”
• service account key is part of service account From the official documentation: “A service account can have up to 10 keys.”
• Cloud Monitoring works with Pub/Sub From the official documentation: “Use Cloud Monitoring and Pub/Sub to set up custom monitoring and alerting policies for exported logs.”
• 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.”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• GKE works with Pub/Sub From the official documentation: “Route Cloud Pub/Sub events to GKE”
• Application Default Credentials secures Cloud Monitoring From the official documentation: “To authenticate to Monitoring, set up Application Default Credentials.”
• Application Default Credentials works with GKE From the official documentation: “To authenticate to GKE, set up Application Default Credentials.”
• Cloud Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
• Cloud Monitoring works with Compute Engine From the official documentation: “Many Google services like Compute Engine send telemetry to 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 Identity and Access Management From the official documentation: “Cloud Run also offers the ability to control access to a service with Identity and Access Management (IAM).”