Domain-specific extensions to the Crisis Response Chain and TRACE / DEBUG / SCALE mnemonics for Kubernetes, service mesh, and cloud platforms.
Placeholder for cloud-native content (K8s, service mesh, observability, multi-cloud). STOP→TRACE→DEBUG→8D and SCALE→SWOT→PESTEL→SET apply broadly; add workflows that fit your stack.
Add pipelines, checklists, or mnemonic adaptations for:
- Kubernetes — pod/namespace/controller lifecycle, scheduling, resource limits, eviction, node failures
- Service mesh — mTLS, traffic policy, split routing, observability in the mesh
- Containers / runtimes — image, registry, runtime, security; when to branch from TRACE to image/build
- Observability (metrics, logs, traces) — where TRACE/DEBUG plug into Prometheus, Jaeger, OpenTelemetry, etc.
- Multi-cloud / platform — cross-region, vendor-specific runbooks that still follow STOP→TRACE→DEBUG
Keep the same structure as the main guide: when-to-use, steps, pitfalls, “combines well with,” real-world example. Link back to TRACE, DEBUG, SCALE, 8D, and METRICS.
- PR adding a
###section under a placeholder (or propose a new one). - Reuse existing mnemonics where possible.
- CONTRIBUTING · FIELD-REPORTS