Gke workload identity vs Gke workload troubleshooting
Gke workload identity is an open-source agent skill for cloud and infrastructure. Gke workload troubleshooting is an open-source agent skill for cloud and infrastructure.
- Gke workload identity is best for diagnose a pod that gets a 403 when calling cloud storage from gke.
- Gke workload troubleshooting is best for why is my pod stuck in crashloopbackoff after the last deploy?.
- What it is
- Gke workload identity is an open-source agent skill for cloud and infrastructure.Gke workload troubleshooting is an open-source agent skill for cloud and infrastructure.
- Best for
- Diagnose a Pod that gets a 403 when calling Cloud Storage from GKEWhy is my pod stuck in CrashLoopBackOff after the last deploy?
- Kind
- SkillSkill
- Pricing
- Open sourceOpen source
- Platforms
- Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, GooseClaude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf, Goose
- GitHub stars
- 24.4K24.4K
- Last commit
- Nov 2026Nov 2026
- License
- Apache-2.0Apache-2.0
- Open source
- Good for
- Diagnose a Pod that gets a 403 when calling Cloud Storage from GKE; Find out why a workload runs as the node's default service account; Fix a missing roles/iam.workloadIdentityUser binding for a Kubernetes ServiceAccountWhy is my pod stuck in CrashLoopBackOff after the last deploy?; My pods are being OOMKilled, is the memory limit too low or is there a leak?; Find out why this deployment cannot pull its image from Artifact Registry.
What Gke workload identity does
Error signature classification
Maps common authentication error messages to the likely failing layer, such as impersonation, target role, or metadata server.
Node pool metadata check
Verifies that the cluster has a workload identity pool and that the node pool uses the GKE metadata server mode.
KSA binding verification
Checks ServiceAccount annotations and IAM policy bindings for both direct principal and legacy impersonation setups.
Target resource IAM audit
Searches Cloud Asset Inventory for the principal's roles and proposes the missing role grant for review.
Metadata server health checks
Inspects gke-metadata-server Pods, logs, and connectivity from the affected Pod, including DNS and egress policy causes.
Read-only remediation boundary
Proposes fixes as commands for a human to run and escalates when root cause remains undetermined.
What Gke workload troubleshooting does
Pod state triage
Maps Pending, CrashLoopBackOff, ImagePullBackOff and ContainerCreating states to the next diagnostic step.
Exit code analysis
Interprets terminated reasons and exit codes such as 137, 128, 0 and 1 to narrow down the cause.
Event signature matching
Recognises FailedScheduling, FailedMount and image pull messages and suggests what each one points to.
OOM classification
Separates container-level, node-level and invisible cgroup v1 out-of-memory kills using logs.
Connectivity checks
Checks service endpoints and network policies when logs show egress timeouts.
Reviewable fix proposals
Drafts manifest patches and gcloud commands for a human to review instead of applying changes.
Gke workload identity vs Gke workload troubleshooting: questions
Is Gke workload identity or Gke workload troubleshooting cheaper?
Both are open source. Compare current plans on each official site.
What is the difference between Gke workload identity and Gke workload troubleshooting?
Gke workload identity is an open-source agent skill for cloud and infrastructure. Gke workload troubleshooting is an open-source agent skill for cloud and infrastructure.
