Archive Topic Map
Reference
A reference is only useful if it can be used mid-incident without ambiguity. This shelf is built for clarity and speed.
Orientation
A curated shelf for study and for retrieval.
How to use reference texts
Reference pages should reduce your search radius. They should name objects precisely and point you to the next proof when reality disagrees.
When you find a term you can’t define operationally, return to the foundations shelf.
A minimal YAML posture
Prefer explicitness: names, labels, selectors, requests, probes, and safe rollout strategy.
A checklist you can apply to most manifests
text
- Labels/selectors aligned and stable
- Requests set (placement economics)
- Readiness meaningful (traffic gate)
- Liveness conservative (kill switch)
- Rollout strategy intentional (headroom)
- Config/secret references explicit (names/keys)
- Ownership clear (controller, not pods)Core references
The fastest way to stabilize vocabulary and patterns.
Reference
TermsLexicon
Definitions plus operational meaning and related reading.
Tutorial
Chapter 14YAML, Deployments, and Services
Manifests, labels/selectors, replicas, and service types with real YAML.
Tutorial
Chapter 13Kubectl and First Deployment
Contexts, basic deploys, service inspection, and cleanup discipline.
Related maps
Adjacent shelves for continued study.
Topic map
MapFoundations
Continue with the adjacent shelf.
Topic map
MapOperations
Continue with the adjacent shelf.
Topic map
MapTroubleshooting
Continue with the adjacent shelf.
Canonical link
Canonical URL: /library/topics/reference