diff --git a/docs/content/manual/release-specific/v1.7.0/test-kubelet-restart-no-pending-pod-event.md b/docs/content/manual/release-specific/v1.7.0/test-kubelet-restart-no-pending-pod-event.md
new file mode 100644
index 0000000000..5021d855e0
--- /dev/null
+++ b/docs/content/manual/release-specific/v1.7.0/test-kubelet-restart-no-pending-pod-event.md
@@ -0,0 +1,22 @@
+---
+Test: restarting Kubelet should not result in repeated "no Pending workload pods ..." event for the workload pod.
+---
+
+## Related issues
+
+- https://github.com/longhorn/longhorn/issues/8072
+
+## Test step
+
+**Given** A [deployment](https://github.com/longhorn/longhorn/blob/master/examples/deployment.yaml) is created.
+
+**When** Kubelet on the node with attached volume of the deployment is restarted.
+```bash
+systemctl restart k3s-agent.service
+```
+
+**Then** Observe the events of the deployment pod.
+```
+kubectl get events --field-selector involvedObject.name=${POD_NAME} -w
+```
+**And** There are no recurring `no Pending workload pods for volume xxx to be mounted` events.