Registry
SKILL Security

gke-workload-identity

Skill that diagnoses GKE Workload Identity Federation authentication failures.

outshift.io Unverified — relayed by outshift.io . Discovered through outshift.io's registry, not anchored by StealthStack. We relay the listing as-is; we have not checked that the URN authority matches the publishing host. seen 4h ago

About

Configures and diagnoses Workload Identity Federation for GKE authentication failures for Pods (403 "iam.serviceAccounts.getAccessToken" / permission denied, "could not find default credentials", or GKE metadata server unreachable) by verifying cluster and node-pool Workload Identity configuration, the Kubernetes ServiceAccount (KSA) to IAM binding (direct principal binding and legacy Google ServiceAccount impersonation), target-resource IAM roles, and gke-metadata-server health. Use when setting up KSA/GSA bindings (`roles/iam.workloadIdentityUser`, `iam.gke.io/gcp-service-account`) or when a Pod cannot authenticate to Google Cloud APIs. Don't use for in-cluster Kubernetes RBAC errors (API-server authorization), general workload crashes (use gke-workload-troubleshooting), or Pod Security Standards and NetworkPolicies (use gke-workload-security).

At a glance

Made for
Developers
Pricing
Free
Access
No sign-in

Category, summary and these details are StealthStack's reading of the publisher's own listing. Check the publisher's page before you rely on them.

Capabilities

The crawler did not record capability metadata for this resource. Inspect the endpoint directly to see what it exposes.

Provenance

Discovered
Relayed by agntcy
Identifier
urn:air:outshift.io:agntcy:gke-workload-identity
Catalog host
outshift.io · via agntcy registry
Anchor check
Not anchored
Last crawled
seen 4h ago

Discovered through outshift.io's registry, not anchored by StealthStack. We relay the listing as-is; we have not checked that the URN authority matches the publishing host. How trust works →

Tags