Difference between revisions of "Kubernetes"
Jump to navigation
Jump to search
m |
m |
||
| Line 1: | Line 1: | ||
| − | Container checkpointing was introduced as an alpha feature in Kubernetes v1.25 and graduated to beta in Kubernetes v1.30. This functionality allows running containers to be transparently checkpointed to persistent storage and later restored to resume execution, or migrated across nodes and clusters. | + | Container checkpointing was introduced as an alpha feature in Kubernetes v1.25 and graduated to beta in Kubernetes v1.30. This functionality allows running containers to be transparently checkpointed to persistent storage and later restored to resume execution, or migrated across nodes and clusters. The content of container checkpoints (e.g., memory pages, open files, network sockets, metadata) can be further analyzed with the [https://github.com/checkpoint-restore/checkpointctl checkpointctl] tool. This allows to perform forensic analysis in case of security incidents (e.g., suspected compromise, data exfiltration) or application failures. |
| − | |||
| − | The content of container checkpoints (memory pages, open files, network sockets, metadata) can be analyzed with the [https://github.com/checkpoint-restore/checkpointctl checkpointctl] tool. | ||
Revision as of 13:33, 7 November 2025
Container checkpointing was introduced as an alpha feature in Kubernetes v1.25 and graduated to beta in Kubernetes v1.30. This functionality allows running containers to be transparently checkpointed to persistent storage and later restored to resume execution, or migrated across nodes and clusters. The content of container checkpoints (e.g., memory pages, open files, network sockets, metadata) can be further analyzed with the checkpointctl tool. This allows to perform forensic analysis in case of security incidents (e.g., suspected compromise, data exfiltration) or application failures.