diff --git a/virt/release_notes/virt-4-20-release-notes.adoc b/virt/release_notes/virt-4-20-release-notes.adoc
index bc3ed9fdb609..6933f99f3da5 100644
--- a/virt/release_notes/virt-4-20-release-notes.adoc
+++ b/virt/release_notes/virt-4-20-release-notes.adoc
@@ -74,6 +74,7 @@ Ensure that you update to the latest z-stream release of your current minor (x.y
 //CNV-58010
 * Using {VirtProductName} on a bare-metal cluster installed on an ARM64 (AARCH64) system is now generally available. For more information, see xref:../../virt/install/preparing-cluster-for-virt.adoc#arm-compatibility_preparing-cluster-for-virt[ARM64 compatibility].
 
+
 //[id="virt-4-20-infrastructure_{context}"]
 //=== Infrastructure
 
@@ -255,6 +256,9 @@ link:https://access.redhat.com/support/offerings/techpreview[Technology Preview
 * {VirtProductName} links a service account token in use by a pod to that specific pod. {VirtProductName} implements a service account volume by creating a disk image that contains a token. If you migrate a VM, then the service account volume becomes invalid. (link:https://issues.redhat.com/browse/CNV-33835[*CNV-33835*])
 ** As a workaround, use user accounts rather than service accounts because user account tokens are not bound to a specific pod.
 
+//CNV-70798
+* When upgrading from {VirtProductName} 4.19 to 4.20, you must remove the `wasp-agent` component before initating the upgrade. For more information about removing the `wasp-agent` component, see xref:../../virt/post_installation_configuration/virt-configuring-higher-vm-workload-density.adoc#virt-removing-wasp-agent_virt-configuring-higher-vm-workload-density[Removing the wasp-agent component].
+
 //[id="virt-4-20-ki-webconsole_{context}"]
 //=== Web console