Every premium and members-only resource for $9.99/month, as a no-commitment subscription. See the plans

PalateKit

Menu

Request a resource

Describe the resource you are missing in one sentence. We will email you when it is published.

0 / 280

Unlock PalateKit

Unlock everything

Plan

Paying means accepting our terms of sale.

Secure payment by Stripe. Receipts and invoices sent by email.

Welcome back

Sign in to install, download or save this resource. A free account is enough for free resources.

Workload Identity Federation troubleshooting for GKE v1.0.0

Use this resource to diagnose and set up Pod authentication to Google Cloud with Workload Identity

New

  • 544 downloads
  • 160 likes
  • 247 saves

Free

Install with the CLI

In a terminal, from the folder you want:

npx --yes palatekit@latest install gke-workload-identity-diagnosis

With no option, the skill goes to ~/.agents/skills/; add --agent claude-code (or codex, cursor…) to target an agent.

First time: connect the CLI with

npx --yes palatekit@latest login

The agent starts from the observed error, such as a 403 on getAccessToken, missing default credentials or an unreachable metadata server. It checks the Workload Identity configuration, the binding between the Kubernetes service account and the Google service account, then the IAM roles on the target resource. You get the diagnosis and fixes to review.

Mostly picked by

Updated November 2, 2026

Card for the “Workload Identity Federation troubleshooting for GKE” skill

Details

Generates with
Your agent's model
Licence
Apache-2.0

Similar resources

View all

What you get

  • SKILL.md: diagnostic method, from the error message to the IAM binding
  • references/attribution.md: attribution rules for gcloud commands

Good fit for

  • A Pod gets a 403 when calling Cloud Storage or BigQuery
  • You are binding a Kubernetes service account to a Google account for the first time

Not for

    Tags

    • workload identity
    • gke
    • iam
    • authentication

    About

    You say

    “My api-worker Pod gets a 403 iam.serviceAccounts.getAccessToken when calling BigQuery: diagnose the binding.”

    Card for the “Workload Identity Federation troubleshooting for GKE” skill

    Skill published by google under the Apache-2.0 license, delivered in its original version.

    Show more

    How to use it

    1. Install the skill in your agent's skills folder
    2. Ask your agent to diagnose and set up Pod authentication to Google Cloud with Workload Identity
    3. Review and adjust the result

    Content preview

    Files

    • LICENSE11.3 KB
    • NOTICE-PALATEKIT.md0.5 KB
    • references/attribution.md1.9 KB
    • SKILL.md18.2 KB

    Origin and licence

    Listed unmodified

    Author
    google
    Source
    github.com/google/skills/tree/81b0e8f8f40513c31b3388e600506e8b48a85bc2/skills/cloud/gke-workload-identity
    Licence
    Apache-2.0

    Notice

    « gke-workload-identity » (google, Apache-2.0) livré dans sa version d'origine : fiche en français et en anglais par PalateKit.

    User reviews

    –

    No ratings yet

    Loading reviews…

    Delete your review?

    Your rating and comment will be removed from the page.