# Infra Pods

> Use when checking pod status, listing running services, investigating crashloops, viewing pod events, or checking resource usage. Use when user says "pods", "qué está corriendo", "pod status", "check pods", "restart", "crashloop", or "pod events".

- Skill: `weorbitant/infra-pods` (Agent Skill)
- Install (CLI): `npx skillmds@latest add weorbitant/infra-pods`
- Raw SKILL.md: https://api.skillmd.com/api/skills/weorbitant/infra-pods/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: weorbitant (https://skillmd.com/u/weorbitant)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/weorbitant/infra-pods

---


# Kubernetes Pod Management

## Overview

Inspect pod status, health, events, and resource usage across cluster environments.

## Pod Status

### List pods for a service

```bash
kubectl --context=<env> get pods -n <namespace> | grep <service>
```

### List all pods in a namespace with status

```bash
kubectl --context=<env> get pods -n <namespace> -o wide
```

### Check for unhealthy pods

```bash
kubectl --context=<env> get pods -n <namespace> | grep -v "Running\|Completed"
```

## Diagnostics

### Pod details and events

```bash
kubectl --context=<env> describe pod <pod> -n <namespace> | tail -30
```

Events show recent scheduling, pulling, starting, and crash info.

### Check restart counts

```bash
kubectl --context=<env> get pods -n <namespace> -o custom-columns=\
NAME:.metadata.name,STATUS:.status.phase,RESTARTS:.status.containerStatuses[0].restartCount,\
AGE:.metadata.creationTimestamp | grep <service>
```

### Pod resource usage

```bash
kubectl --context=<env> top pods -n <namespace> | grep <service>
```

### Environment variables (non-secret)

```bash
kubectl --context=<env> exec -n <namespace> <pod> -- env | grep -iv "pass\|secret\|token\|key" | sort
```

### Check which image/version is running

```bash
kubectl --context=<env> get pod <pod> -n <namespace> \
  -o jsonpath='{.spec.containers[0].image}'
```

The image tag is the **GitHub Actions run ID** (`databaseId`). To find which PR/commit it corresponds to:

```bash
# Cross-reference image tag with CI runs on main
gh run list --repo <org>/<repo> --branch main --json databaseId,displayTitle,headSha \
  | jq '.[] | select(.databaseId == <image-tag>)'
```

## Common Namespaces

Read namespace names from the project's CLAUDE.md (`## Infrastructure` section). Typical patterns:
- Application services: one namespace per cluster (e.g. `plataformadato`)
- Shared infrastructure (RabbitMQ, monitoring): separate namespace (e.g. `shared-infra`)

## Rollout Management

### Check deployment status

```bash
kubectl --context=<env> get deploy -n <namespace> | grep <service>
```

### Restart a deployment (rolling)

> ⚠️ **ALWAYS ask for explicit confirmation before running this command, in any environment.**
> State clearly: what deployment will restart, in which environment, and what the impact is (brief downtime during rollout).
> Do NOT run without the user saying "yes", "proceed", or equivalent.

```bash
kubectl --context=<env> rollout restart deployment/<deployment> -n <namespace>
```

### Check rollout history

```bash
kubectl --context=<env> rollout history deployment/<deployment> -n <namespace>
```