You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/posts/checkpointing.md
+16-5Lines changed: 16 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,18 +6,26 @@ authors: ["Kapil Agrawal"]
6
6
comments: false
7
7
---
8
8
9
+
A checkpoint involves taking a snapshot of a running process or a set of processes and save their entire state to disk as a collection of files, known as image files. This state includes memory contents, open file descriptors, network connections, CPU registers, and other process-related information.Kubernetes v1.25 introduced the concept of creating stateful container checkpoints for forensic analysis without stopping a pod. In this blog post I am going to cover the steps involved with checkpointing a pod running on k3s cluster.
10
+
9
11
## Identify our Pod of interest
10
12
11
-
Find the node where the pod is currently running
13
+
Let's say we want to checkpoint our `netshoot` pod. First we need to locate the node where the pod is currently running
12
14
13
15
```sh
14
16
kubectl get pod -o wide
17
+
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
0 commit comments