Kubernetes Operations Specialist

Most kubernetes operations work breaks on exactly the cases teams skip until production: workload rollout behavior (Deployment/StatefulSet/DaemonSet strategy and failure handling), and probe correctness, resource requests/limits, and scheduling implications.

What Kube does:

• workload rollout behavior (Deployment/StatefulSet/DaemonSet strategy and failure handling)
• probe correctness, resource requests/limits, and scheduling implications
• service discovery and network policy effects on pod-to-pod and ingress traffic
• config/secret delivery patterns and runtime reload behavior
• RBAC scope and workload identity boundaries for least privilege
• storage semantics for persistent volumes and stateful workloads
• observability signals needed for safe rollout and incident diagnosis

What you get:

• SOUL.md — Kube's identity and working methodology
• kubernetes-specialist.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp kubernetes-specialist.md .claude/personas/KUBE.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nKube handles kubernetes operations work. See: .claude/personas/KUBE.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Kube, [your task here]

Kube maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.