gke-ai-troubleshooting-jobset-interruption skillA
gke-ai-troubleshooting-jobset-interruption is agent-read markdown (skill) from gke-labs/kube-agents: Diagnoses GKE JobSet interruptions, restarts, and preemptions for AI/ML training workloads autonomously. Use when troubleshooting JobSet restart loops, spot VM preemptions, node readiness failures, host VM issues, or coordinator worker crashes. Don't use for general GKE cluster creation, basic workload deployment, or non-JobSet application issues..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# GKE JobSet Interruption Troubleshooting
Use this skill to systematically diagnose and resolve JobSet interruptions,
restarts, and preemptions on GKE clusters hosting large-scale AI/ML workloads.
## ⚠️ Prerequisites & Sandbox Rules
- JobSet metrics package must be enabled in `kube-state-metrics` for your
cluster.
- Cloud Logging and Cloud Monitoring enabled for the Google Cloud Project.
- **Autonomous & Sandbox Execution Rule**: If API queries, tools, or commands
encounter `403 Permission Denied`, authentication errors, or network
isolation, **do NOT enter authentication or credential troubleshooting
loops**. Populate the query templates with the acquired variables
(`{project_id}`, `{cluster_name}`, `{workload_name}`, `{start_time}`,
`{end_time}`), inspect any locally staged telemetry or mock data files if
available, and complete the diagnostic workflow and resolution
recommendations autonomously.
## 🔍 Diagnostic Workflow
### Step 0: Context Acquisition & Time Window Definition
Independently gather context using tools, workspace files, environment details,
or user prompt context:
- **Project ID** (`{project_id}`)
…Read the whole file at its exact version.
How to install
mdr add gke-labs/kube-agents/gke-ai-troubleshooting-jobset-interruption@git:20260807.d47bdf1mdr add gke-labs/kube-agents/gke-ai-troubleshooting-jobset-interruption@sha256:597115bc05f125caPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_jjakn5enygxkq5mp)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11027 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
gke-labs/kube-agents · 64 stars · license Apache-2.0 · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jjakn5enygxkq5mp GET https://markdownregistry.com/api/v1/resolve?ref=gke-labs/kube-agents/gke-ai-troubleshooting-jobset-interruption GET https://markdownregistry.com/api/v1/blob/597115bc05f125cae446b866c76c78b841dea9e65d80a57f0870b0cd8667ab7e
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.