After a city worker node reboots, local container logs that were ne…

Question

After a city worker node reboots, local container logs that were never shipped elsewhere are gone. What durability lesson should administrators take?

Accepted Answer

Without centralized log shipping or remote retention, container log history on a node is ephemeral and can disappear with node or runtime lifecycle events. — Local container logs live on the node’s filesystem like sticky notes on a cubicle wall—reboot the desk and they’re gone unless you mailed copies downtown.

Answer

kube-apiserver permanently stores every Pod’s stdout in etcd for the life of the cluster.

Answer

Service ClusterIP objects automatically archive Pod logs for thirty days.

Answer

Ingress controllers persist application logs into PersistentVolumeClaims by default.

After a city worker node reboots, local container logs that were never shipped elsewhere are gone. What durability lesson should administrators take?

Short Explanation

Full Explanation