Gke workload troubleshooting vs Pathways workload
Gke workload troubleshooting is an open-source agent skill for cloud and infrastructure. Pathways workload is an open-source agent skill for cloud and infrastructure.
- Gke workload troubleshooting is best for why is my pod stuck in crashloopbackoff after the last deploy?.
- Pathways workload is best for find out why a pathways jax training job crashed on gke tpus.
- What it is
- Gke workload troubleshooting is an open-source agent skill for cloud and infrastructure.Pathways workload is an open-source agent skill for cloud and infrastructure.
- Best for
- Why is my pod stuck in CrashLoopBackOff after the last deploy?Find out why a Pathways JAX training job crashed on GKE TPUs
- 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
- Why 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.Find out why a Pathways JAX training job crashed on GKE TPUs; Diagnose an IFRT proxy connection failure between client and Pathways server; Investigate a Pathways inference LeaderWorkerSet that stopped making progress
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.
What Pathways workload does
Earliest-error triage
Sweeps all workload containers for segfaults, tracebacks, OOM kills and permission errors, ordered by first occurrence.
Container-by-container playbooks
Guides log inspection for the user workload, IFRT proxy, resource manager, workers and colocated sidecar in logical order.
Known failure scenarios
Maps specific error messages such as DEADLINE_EXCEEDED and ImagePullBackOff to documented causes and fixes.
Preemption and interruption tracing
Checks infrastructure interruptions and pod events to find who sent a SIGTERM and which TPU failed first.
Version compatibility checks
Compares JAX, jaxlib and pathwaysutils versions with Pathways image tags and build labels.
Log query helper script
A Python script wraps gcloud logging queries with time windows and actions for summaries, events and OOMs.
Gke workload troubleshooting vs Pathways workload: questions
Is Gke workload troubleshooting or Pathways workload cheaper?
Both are open source. Compare current plans on each official site.
What is the difference between Gke workload troubleshooting and Pathways workload?
Gke workload troubleshooting is an open-source agent skill for cloud and infrastructure. Pathways workload is an open-source agent skill for cloud and infrastructure.
