docs: add workaround

docs/docs-content/release-notes/known-issues.md

@@ -16,7 +16,7 @@ The following table lists all known issues that are currently active and affecti
 
 | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Workaround                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Publish Date   | Product Component     |
 | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- | --------------------- |
-| When you use a content bundle to provision a new cluster without using the local Harbor registry, it's possible for the images to be pulled from external networks instead of from the content bundle, consuming network bandwidth. If your Edge host has no connection to external networks or if it cannot locate the image on a remote registry, some pods may enter the `ImagePullBackOff` state at first, but eventually the pods will be created using images from the content bundle. | No workarounds for connected clusters: it's possible that extra bandwidth will be consumed, but it will not result in cluster creation failure. For airgap clusters, the `ImagePullBackOff` error will eventually resolve on its own and there is no action to take.                                                                                                                                                                                                                                                                                                                                            | July 11, 2024  | Edge                  |
+| When you use a content bundle to provision a new cluster without using the local Harbor registry, it's possible for the images to be pulled from external networks instead of from the content bundle, consuming network bandwidth. If your Edge host has no connection to external networks or if it cannot locate the image on a remote registry, some pods may enter the `ImagePullBackOff` state at first, but eventually the pods will be created using images from the content bundle. | For connected clusters, you can make sure that the remote images are not reachable by the Edge host, which will stop the Palette agent from downloading the image and consuming bandwidth, and eventually the cluster will be created using images from the content bundle. For airgap clusters, the `ImagePullBackOff` error will eventually resolve on its own and there is no action to take.                                                                                                                                                                                                                | July 11, 2024  | Edge                  |
 | When you add a new VMware vSphere Edge host to an Edge cluster, the IP address may fail to be assigned to the Edge host after a reboot.                                                                                                                                                                                                                                                                                                                                                      | Review the [Edge Troubleshooting](../troubleshooting/edge.md) section for workarounds.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | July 9, 2024   | Edge                  |
 | When you install Palette Edge using an Edge Installer ISO with a RHEL 8 operating system on a Virtual Machine (VM) with insufficient video memory, the QR code in the registration screen does not display correctly.                                                                                                                                                                                                                                                                        | Increase the video memory of your VM to 8 MB or higher. The steps to do this vary depending on the platform you use to deploy your VM. In vSphere, you can right click on the VM, click **Edit Settings** and adjust the video card memory in the **Video card** tab.                                                                                                                                                                                                                                                                                                                                           | July 9, 2024   | Edge                  |
 | Custom Certificate Authority (CA) is not supported for accessing Azure AKS clusters. Using a custom CA prevents the `spectro-proxy` pack from working correctly with Azure AKS clusters.                                                                                                                                                                                                                                                                                                     | No workaround is available.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | July 9, 2024   | Packs, Clusters       |