Skip to content

Commit 6798680

Browse files
adrianreberTim Bannister
andcommitted
Add link to checkpointing follow-up article
Co-authored-by: Tim Bannister <[email protected]> Signed-off-by: Adrian Reber <[email protected]>
1 parent 5087c55 commit 6798680

File tree

1 file changed

+8
-0
lines changed
  • content/en/blog/_posts/2022-12-05-forensic-container-checkpointing

1 file changed

+8
-0
lines changed

content/en/blog/_posts/2022-12-05-forensic-container-checkpointing/index.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -207,3 +207,11 @@ and without losing the state of the containers in that Pod.
207207
You can reach SIG Node by several means:
208208
- Slack: [#sig-node](https://kubernetes.slack.com/messages/sig-node)
209209
- [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-node)
210+
211+
## Further reading
212+
213+
Please see the follow-up article [Forensic container
214+
analysis][forensic-container-analysis] for details on how a container checkpoint
215+
can be analyzed.
216+
217+
[forensic-container-analysis]: /blog/2023/03/10/forensic-container-analysis/

0 commit comments

Comments
 (0)