Skip to content

Archive Topic Map

Operations

Operations is not a bag of commands. It is a protocol: observe → narrow → act → confirm → memorialize.

Orientation

A curated shelf for study and for retrieval.

The operator protocol

The shrine language is ceremonial because it is repeatable. Under pressure you need a sequence, not inspiration.

This shelf is built around stable workflows: evidence first, minimal change, explicit verification.

  • Prefer read-only diagnosis until you can name the failure mode.
  • Change one thing at a time; preserve attribution.
  • Treat rollback as a first-class capability, not a last resort.

Minimal commands that surface truth

These commands won’t solve incidents, but they will stop you from lying to yourself.

kubectl

shell

kubectl get pods -n <ns> -o wide
kubectl describe pod <pod> -n <ns>
kubectl logs <pod> -n <ns> --previous --all-containers=true
kubectl get events -n <ns> --sort-by=.lastTimestamp | tail -n 40

Core texts

Rollout posture, incident discipline, and the governance of change.

Practice and diagnostics

Labs and atlas entries built for real failure modes.

Related maps

Adjacent shelves for continued study.

Canonical link

Canonical URL: /library/topics/operations