Tag
© 2026 Hashnode
TL;DR Least privilege is a loop, not a policy you write once: grant what a workload demonstrably needs, watch what it actually uses (CloudTrail), remove the rest, repeat. Prefer roles and temporary c

TL;DR State is Terraform's memory of what it manages. Lose it or corrupt it and Terraform doesn't lose your infrastructure — it loses the map to it, which from the operator's chair is nearly as bad.

TL;DR Requests are what the scheduler spends; limits are what the kernel enforces. A pod is placed based on its requests, and killed or throttled based on its limits. CPU and memory fail differently:

TL;DR Almost every pod failure is diagnosed with the same four moves, in order: kubectl describe → events → kubectl logs (including --previous) → kubectl debug / exec. CrashLoopBackOff is a symptom,
