Weekly · Infrastructure · SignalIssue #42 Live
█

The Newsletter That Reads Your
Runbook Before You Do.

Weekly 5-minute dissections of Kubernetes outages, Docker misconfigs, and container war stories. Written for on-call engineers debugging at 2 AM — not for the blog post that explains it six months later.

●12,400 platform engineers·42 issues published·Free forever
Interactive Preview
kubectl get pods -n production
NameStatusAge

↑ Click any pod to run diagnostic analysis

>CrashLoopBackOff>OOMKilled>ImagePullBackOff>Pending → Running>CPU Throttled>Node Pressure>Service Mesh Migration>ECS vs K8s>exit code 137>Liveness Probe Failed>etcd Compaction>HPA Flapping>CrashLoopBackOff>OOMKilled>ImagePullBackOff>Pending → Running>CPU Throttled>Node Pressure>Service Mesh Migration>ECS vs K8s>exit code 137>Liveness Probe Failed>etcd Compaction>HPA Flapping
> compare --platforms=5 --dimensions=12

Container Orchestration Decoded

Every cell is a decision point. Every link is an issue that went deeper. This is what five platforms look like when you strip out the marketing.

●Best in class
●Good
●Acceptable
●Avoid
Click any row to expand analysis
Dimension
K8sSelf-hosted
ECSManaged
FlyPaaS
NomadHashiCorp
GKEManaged K8s
Cold Start Latency
●8–45s
●12–60s
●< 2s
●5–20s
●6–30s
Secret Management
●etcd (base64)
●SSM + Secrets Manager
●fly secrets set
●Vault native
●Secret Manager CSI
Auto-scaling Granularity
●HPA + KEDA
●Target Tracking
●Scale-to-zero native
●Autoscaler plugin
●VPA + HPA + NAP
Built-in Observability
●Minimal (metrics-server)
●CloudWatch native
●Prometheus + Grafana
●Telegraf + Consul
●Cloud Monitoring
Multi-region Deployment
●Federation (complex)
●Manual per-region
●fly regions add
●Multi-region jobs
●Multi-cluster Ingress
Cost Visibility
●Kubecost (OSS)
●Cost Explorer tags
●Per-machine billing
●None native
●GKE Cost Insights
Service Mesh Ready
●Istio / Linkerd / Cilium
●App Mesh (deprecated)
●WireGuard native
●Consul Connect
●Anthos Service Mesh
Rollback Speed
●kubectl rollout undo
●Circuit breaker
●fly deploy --strategy
●Job revert
●Deployment rollout
Stateful Workloads
●StatefulSets + PVC
●EFS mount targets
●fly volumes
●CSI plugins
●Persistent Disks + CSI
Time to Production
●14–30 days
●3–7 days
●< 1 day
●5–10 days
●7–14 days
Community Plugin Count
●1,200+ Helm charts
●~180 integrations
●~40 extensions
●~200 integrations
●Full K8s + GCP
Series A Fit Score
●7.2 / 10
●7.8 / 10
●8.9 / 10
●6.5 / 10
●8.1 / 10

Read This Week's Issue Free

Issue #42: ECS vs K8s before Series A — the 8-factor decision framework your investors won't have.

Read Free Issue →
Latest IssueFeb 27, 2026 · 4 min read

Issue #42: The Redis OOMKill Pattern

How three startups lost 47 minutes of on-call time to a two-line config fix.

Get Weekly in App →
deploy-issue-42 — bash
• Redis OOMKill on startup → missing maxmemory config in 73% of affected clusters
• Fix: maxmemory 400mb + maxmemory-policy allkeys-lru prevents restart cascade
• Three production outages last month shared this exact root cause
• Estimated MTTR improvement: 47 minutes → 4 minutes with this runbook
42 issues · 12,400 engineers subscribedexit 0 ✓
#41Performance

Right-sizing K8s resource requests without guessing

#40Cost

Why your K8s bill is always a surprise

#39Databases

Running Postgres on K8s — the honest 2026 assessment

> kubectl describe community

Engineers Who Ship on Sundays

12,400 platform engineers. Zero fluff. One signal per week.

12,400

Engineers subscribed

42

Issues published

4.9/5

Avg read rating

< 5min

Minutes per issue

“Issue #38 on CPU throttling saved us 3 hours of debugging. We had the exact same CFS quota issue. Forwarded it to the entire platform team.”
MO

Marcus Oyelaran

Staff Platform Engineer · Ramp

K8s / GKE
“The Redis OOM issue dropped into my inbox at 7 AM. By 9 AM I'd already patched our staging cluster. That's the Deploy ROI — zero lag between insight and action.”
PK

Priya Krishnamurthy

DevOps Lead · Razorpay

ECS / Docker
“Every other newsletter explains what happened. Deploy explains why it happened and gives you the kubectl commands to check if you're next. That's the difference.”
TW

Tobias Wendt

CTO · Stacker (Series A)

Startup / EKS
“I read it on the train before standup. By the time I'm at my desk I've already got a PR open for the thing we were definitely going to hit in three weeks.”
AN

Aisha Nkemdirim

SRE · Deliveroo

Nomad / Consul
“Replaced three Slack channels, two RSS feeds, and one very expensive consultant. The comparison tables alone are worth the subscription.”
DP

Daniel Park

VP Engineering · Lemon8

K8s / Cilium
“The issue on Fly.io multi-region made me reconsider our entire ECS migration plan. That's a $200k infra decision influenced by a 4-minute read.”
CR

Camille Rousseau

Infrastructure Lead · Pennylane

Fly.io / GKE
> deploy install --platform=desktop

Signal in Your Pocket. Zero Noise.

Every Friday at 06:00 UTC. Read in 5 minutes. Remember for months. The Deploy app delivers every issue with offline reading, push alerts on major outage patterns, and a searchable archive of all 42 issues.

Offline reading

Full issue cached on device. Read on the train, in the war room.

Outage alerts

Push notification when a new incident pattern matches your stack.

Full archive search

All 42 issues, full-text searchable. Find the Redis issue at 3 AM.

Free forever · No account required · Unsubscribe in 2 taps

Issue #42 — ECS vs K8s before Series A is live