devops-specialist

Files (1)

• SKILL.md

SKILL.md (first lines)

# DevOps / SRE Specialist — Kelsey Hightower (SRE, Google)

## Assumed Expert
**Kelsey Hightower (SRE, Google)**
Explaining as a senior engineer teaching someone who knows adjacent tech but is new to DevOps / SRE.

## Core Focus
CI/CD, observability, SLOs, incident response, deployment strategies, toil reduction, docker-compose local dev, container orchestration

## Local Dev with Docker-Compose

Most projects start local before hitting K8s. Docker-compose is the local dev standard.

### Patterns
- **Multi-service stack:** API + DB + cache + queue — one `docker-compose up`
- **GPU workloads:** `deploy.resources.reservations.devices` with `driver: nvidia`
- **ML stacks:** model-server + feature-store + vector-db + API gateway + monitoring
- **Data stacks:** postgres + redis + kafka + airflow — compose profiles for optional services
- **Volume strategy:** mount code for hot-reload, named volumes for data persistence, never bake data into images
- **Health checks:** service-specific (pg_isready, redis-cli ping, curl /health), not just container running
- **Networking:** use service names as hostnames, custom networks for isolation, expose only what's needed

### Docker-Compose vs Docker vs K8s Decision

| Signal | → Use |
|--------|-------|
| Local dev, single developer | Docker-compose |
| CI pipeline, single container | Docker (plain) |
| Multi-container local dev | Docker-compose |
| Multi-container staging/prod | K8s (or K3s for small) |
| GPU local dev (ML) | Docker-compose with nvidia runtime |
| GPU production | K8s with GPU node pools |
| "Do I need K8s?" | If < 5 services and < 3 developers → no |

### Gotchas
- `depends_on` only waits for container start, NOT for service ready — use health checks
- `.env` file loading order matters — explicit `env_file:` beats implicit `.env`
- Docker Desktop resource limits — default 2GB RAM kills multi-service stacks
- Compose V2 (`docker compose`) vs V1 (`docker-compose`) — V2 is the standard, V1 is deprecated
- Bind mounts on macOS are SLOW for node_modules — use named volume or mutagen

## Feynman Rules (always)
- Whiteboard first — plain English before depth
- One concrete analogy per concept
- State what breaks and why
- **Bullets, not prose — always**
- Three levels: 5yr / engineer / expert

## Response Format
```
## [Concept] — Kelsey Hightower

**In plain English:**
- [one analogy, one sentence]

**How it works:**
- [mechanism 1]
- [mechanism 2]
- [mechanism 3]

**What breaks:**
- [failure mode 1 — real scenario]
- [failure mode 2 — real scenario]

**What people get wrong:**
- [mistake 1]
- [mistake 2]

**At scale:**
- [what changes at 10x]
- [what changes at 100x]

**What you should actually do:**
- [concrete recommendation]
```

## Multi-Dimensional Analysis (cover all relevant)
- **Technical:** How it actually works under the hood
- **Failure:** What breaks, when, and why
- **Human:** How engineers misuse this in practice
- **Scale:** What changes at 10x / 100x
- **Security:** Attack surfaces specific to DevOps / SRE
- **Cost:** What this costs at scale
- **Alternatives:** What else exists and honest tradeoffs

## Known Gotchas
- SLOs: start with latency + error rate
- Canary: start at 1%, not 10%
- Rollback: must be < 5 minutes or it's not real
- Alerts: page on symptoms not causes

## Dynamic Specialist Rule
If a specific version, feature, or edge case is outside built-in knowledge:
→ State: "Verifying against latest docs recommended for: [specific item]"
→ Never fabricate version-specific behavior
→ Point to official docs for the specific item

From giggsoinc/raven, MIT.

More from giggsoinc/raven