Ephemeral Container Storage Data Loss

Container Lifecycle and Storage In container orchestration systems like Kubernetes, storage is categorized by its relationship to the pod or container lifecycle. Ephemeral storage (option C) is temporary, local storage tied directly to the life of a container or pod. When a container crashes, stops, or restarts, the ephemeral storage is wiped clean, and the container starts again from its original state. This is the defining characteristic of ephemeral storage.

Persistence vs. Transience Persistent volumes (option B) are the exact opposite; they exist independently of the container lifecycle and are explicitly designed to survive container restarts, rescheduling, or pod terminations. Therefore, option B is incorrect for this scenario.

Underlying Storage Architectures Object (option A) and Block (option D) describe backend storage architectures rather than container-specific lifecycle behaviors. While a container might utilize block or object storage as the backend for a volume, the key factor determining data retention upon a container restart is whether the volume is mounted as ephemeral or persistent. Ephemeral storage often utilizes the node's local block storage under the hood, but because it is not mounted as a persistent volume, it is destroyed with the container. As one comment correctly summarizes, ephemeral storage is tied to the container lifecycle, meaning any data written to it is permanently lost upon a restart, leaving the container with a "clean slate".

Conclusion Because the question specifically asks for the storage type that loses data after a restart, the correct and only valid choice is C.