# Triage Pending Pods

> Diagnose pods stuck in Pending and identify scheduling constraints.

- **Type:** Skill
- **Install:** `agentstack add skill-bregman-arie-devops-sre-skills-triage-pending-pods`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [bregman-arie](https://agentstack.voostack.com/s/bregman-arie)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [bregman-arie](https://github.com/bregman-arie)
- **Source:** https://github.com/bregman-arie/devops-sre-skills/tree/main/skills/kubernetes/triage-pending-pods

## Install

```sh
agentstack add skill-bregman-arie-devops-sre-skills-triage-pending-pods
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

## When to use

Use when pods remain in `Pending` longer than expected.

## Preconditions

- You can access pod events and node capacity information.

## Procedure

1. Identify which pods are pending and for how long.
2. Inspect pod scheduling events to find the exact constraint.
3. Classify the blocker: insufficient resources, taints/tolerations, affinity, PV binding, quotas, or image pull.
4. Confirm whether the blocker is local (one namespace/workload) or global (cluster capacity).
5. Choose the lowest-risk remediation.

## Decision points

- `Insufficient cpu/memory`: scale cluster, reduce requests, or shed load.
- `taint {node.kubernetes.io/...}`: add toleration only if correct.
- `pod affinity/anti-affinity`: loosen rules if they are too strict.
- `unbound immediate PersistentVolumeClaims`: investigate storage class/provisioner.
- `exceeded quota`: adjust quota or reduce consumption.

## Verification

- Pods transition from `Pending` to `Running`.
- Scheduling events stop reporting the constraint.

## Rollback / undo

- Revert scheduling policy changes (affinity/tolerations) if they increase blast radius.
- Revert quota changes if they cause noisy neighbor impact.

## Escalation

- Platform team for cluster capacity or storage provisioner issues.
- Service owner for incorrect requests/affinity rules.

## Examples

```bash
kubectl -n  get pod 
kubectl -n  describe pod 
kubectl get nodes
```

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [bregman-arie](https://github.com/bregman-arie)
- **Source:** [bregman-arie/devops-sre-skills](https://github.com/bregman-arie/devops-sre-skills)
- **License:** Apache-2.0

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-bregman-arie-devops-sre-skills-triage-pending-pods
- Seller: https://agentstack.voostack.com/s/bregman-arie
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.