#Terraform and
#Kubernetes do not reduce this gap -- they shift it. Terraform manages
cloud resource declarations but still requires manual secret rotation, manual runner
registration, and manual responses to OOM events unless paired with autoscaling and
pod disruption budgets. Kubernetes adds liveness probes, resource limits, and automatic
pod restarts, which would have caught the etcd memory balloon automatically via
`resources.limits.memory` and restarted the pod before it consumed the host. But
Kubernetes itself runs on the same VM here, making the cluster a tenant of the system
it is supposed to manage -- which is why kubelet's own `MemoryPressure` condition
appeared in the logs as a symptom of the problem it was meant to prevent.