gke-ai-troubleshooting-tpu-vbar-oom skillA
gke-ai-troubleshooting-tpu-vbar-oom is agent-read markdown (skill) from gke-labs/kube-agents: Diagnoses and prevents vbar_control_agent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbar_control_agent crashes, memory cgroup OOMs in serial console logs, tpu-device-plugin metrics checksum corruption errors, or custom TPU metrics collection conflicts on GKE TPU v6e nodes. Don't use for general non-TPU container OOM troubleshoo.
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
# TPU Connection Failure and VBAR OOM Troubleshooting
Use this skill to systematically diagnose and prevent `vbar_control_agent`
segfaults and Out-Of-Memory (OOM) errors on TPU v6e nodes.
## ⚠️ Prerequisites
- Cloud Logging must be enabled for the project.
- Access to the project and cluster via `gcloud` or equivalent tool.
## 🔍 Diagnostic Workflow
### Step 0: Context Acquisition & Time Window Definition
Independently gather required context using available GCP/GKE tools or use the
provided `{variable}` placeholders:
- `{project_id}`: The GCP Project ID (e.g., `customer-ai-project-123`).
- `{cluster_name}`: The GKE Cluster Name (e.g., `tpu-cluster-prod`).
- `{node_name}`: The Node Name or Instance ID (e.g., `tpu-node-1`).
- `{workload_name}`: The Workload Name / JobSet Name (e.g.,
`my-training-job-456`).
- `{namespace}`: The Workload Namespace.
- `{issue_time}`: The timestamp of the issue (e.g., `2026-04-14T20:00:00Z`).
#### Time Handling & Execution Rules
1. **Window Calculation**: If an issue timestamp `{issue_time}` is provided,
calculate the query time window as `[{issue_time} - 30m]` to
`[{issue_time} + 30m]`.
…Read the whole file at its exact version.
How to install
mdr add gke-labs/kube-agents/gke-ai-troubleshooting-tpu-vbar-oom@git:20260807.d47bdf1mdr add gke-labs/kube-agents/gke-ai-troubleshooting-tpu-vbar-oom@sha256:92762cce7dd9d0d0Pin 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_5324dxnwq6iwg6s4)
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 (6358 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_5324dxnwq6iwg6s4 GET https://markdownregistry.com/api/v1/resolve?ref=gke-labs/kube-agents/gke-ai-troubleshooting-tpu-vbar-oom GET https://markdownregistry.com/api/v1/blob/92762cce7dd9d0d090ec4c8524dac875564f5a825fa5b990d44afbeb81dbb170
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.