From 67d988dbf6cf9a1673a8399acdb24537cbaa2154 Mon Sep 17 00:00:00 2001
From: Adrian Reber <areber@redhat.com>
Date: Tue, 7 Mar 2023 19:30:02 +0100
Subject: [PATCH] Add link to checkpointing follow-up article

Signed-off-by: Adrian Reber <areber@redhat.com>
---
 .../2022-12-05-forensic-container-checkpointing/index.md  | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/content/en/blog/_posts/2022-12-05-forensic-container-checkpointing/index.md b/content/en/blog/_posts/2022-12-05-forensic-container-checkpointing/index.md
index 14293556a43ba..82ad6274b39b2 100644
--- a/content/en/blog/_posts/2022-12-05-forensic-container-checkpointing/index.md
+++ b/content/en/blog/_posts/2022-12-05-forensic-container-checkpointing/index.md
@@ -207,3 +207,11 @@ and without losing the state of the containers in that Pod.
 You can reach SIG Node by several means:
 - Slack: [#sig-node](https://kubernetes.slack.com/messages/sig-node)
 - [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-node)
+
+## Further reading
+
+Please see the follow-up article [Forensic container
+analysis][forensic-container-analysis] for details how a container checkpoint
+can be analyzed.
+
+[forensic-container-analysis]: https://kubernetes.io/blog/2023/03/10/forensic-container-analysis/