# K8S Verify

> Post-deploy Kubernetes verification checklist for namespace detection, rollout health, endpoints, events, and optional log analysis.

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

---


# Kubernetes Verification

Use this skill after a Kubernetes deployment, rollout restart, or suspicious
cluster state.

## Relationship to Copilot built-ins

- Use this as a custom operational workflow because Copilot has no built-in
  Kubernetes post-deploy verifier.
- Use `.github/copilot-instructions.md` and deployment manifests as the source
  of truth before issuing commands.

## Verification order

1. Confirm cluster context and namespace
2. Check pod readiness and failures
3. Check rollout status with a timeout
4. Verify services have endpoints
5. Inspect recent warning/error events
6. Run HTTP health checks only when endpoints are documented
7. Inspect logs only for failed or warning pods unless a full pass was requested

## Pod verdicts

- `Running` with all containers ready -> PASS
- partial readiness or `Pending` -> WARN
- `CrashLoopBackOff`, `ImagePullBackOff`, `Error` -> FAIL

## Common failure patterns to surface

- missing or unhealthy probes
- rollouts stuck beyond the timeout
- services with zero endpoints
- recent `BackOff`, `FailedMount`, `FailedPull`, or `Unhealthy` events
- readiness paths or ports guessed instead of verified

## Report format

Return a compact table or bullet summary covering:

- Pods
- Rollouts
- Endpoints
- Events
- HTTP health
- Logs
- Final verdict: `HEALTHY`, `DEGRADED`, or `UNHEALTHY`

## Examples

- **Healthy rollout:** Confirm namespace and context, verify pods are ready,
  rollout status succeeds within timeout, services have endpoints, and no recent
  warning events appear; return `HEALTHY`.
- **Degraded rollout:** Pods are running but one deployment has partial
  readiness and warning events; return `DEGRADED` with the specific failing
  checks instead of a generic status summary.

## Guardrails

- Never guess namespace, pod names, ports, or health paths.
- Always use a timeout for rollout checks.
- Clean up temporary port-forwards.

## Do Nots

- Do not run HTTP health checks against guessed ports or paths.
- Do not treat stale cluster context as acceptable if namespace or target
  deployment is ambiguous.
- Do not leave helper resources such as temporary port-forwards behind after the
  verification run.

## Closed Decisions

- Verification follows the declared order: context, pods, rollout, endpoints,
  events, HTTP health, then logs.
- Namespace, pod names, ports, and health paths must be verified rather than
  inferred.
- Rollout checks always use a timeout.
- Final verdicts are limited to `HEALTHY`, `DEGRADED`, or `UNHEALTHY`.