Kubernetes

Align connect, header, body, idle, and upstream deadlines so one layer does not outlive another.

A reproducible multi-stage build and minimal runtime reduce drift, size, and attack surface.

Choose buckets around decisions and inspect distributions; averages conceal the users waiting longest.

Instrument bounded dimensions and user outcomes; labels are a data model with a capacity cost.

Keep instrumentation semantic and portable while isolating exporter and sampling policy.

A rollout is safe when new instances prove dependencies, warmup, and service health before receiving load.

Start from operator questions and put traffic, errors, latency, saturation, and deploy context together.

Requests drive placement; limits change runtime behavior; both need measurements from realistic load.

Concurrency equals arrival rate times time in system, giving a fast check for queues and resource demand.

Logs need stable event names, correlation, severity discipline, and deliberate data minimization.

Propagate context, name spans by operation, and attach identifiers without recording sensitive payloads.

Stabilize impact, preserve a timeline, test hypotheses with signals, and separate recovery from diagnosis.

Use short-lived identity-bound credentials and design renewal and revocation as runtime paths.

An SLO connects user-visible success to an error budget and concrete release decisions.

Startup, readiness, and liveness answer different questions and should trigger different actions.