docs(images): add new images for encryption and storage class documen…

versioned_docs/version-v1.6/image/image-security.md

@@ -39,7 +39,7 @@ Prepare the following resources:
 
 - Secret: A Kubernetes secret is used as the passphrase of dm_crypt. You must specify the value of the `CRYPTO_KEY_VALUE` field. All other fields are fixed.
 
-  ![](/img/v1.4/image/create-encryption-used-secret.png)
+  ![](/img/v1.3/image-hv/create-encryption-used-secret.png)
 
   Example of a secret:
 
@@ -74,7 +74,7 @@ Prepare the following resources:
 
 - StorageClass: Images are encrypted using Longhorn, so required fields must be passed to the Longhorn CSI Driver. You can specify the encryption secret when creating a StorageClass. For more information, see [Image StorageClass](./upload-image#image-storageclass). 
 
-  ![](/img/v1.4/image/create-storage-class.png)
+  ![](/img/v1.3/image-hv/create-storage-class.png)
 
   Example of a StorageClass:
 
@@ -172,4 +172,4 @@ You cannot perform the following actions:
 
 - Export a new image from an encrypted image
 - Download an encrypted image
-- Upload an encrypted image
+- Upload an encrypted image

versioned_docs/version-v1.6/image/upload-image.md

@@ -40,7 +40,7 @@ This issue is fixed in v1.6.1.
 
 :::
 
-![](/img/v1.2/upload-image.png)
+![](/img/v1.3/image-hv/upload-image.png)
 
 </TabItem>
 <TabItem value="api" label="API">
@@ -92,7 +92,7 @@ Currently, qcow2, raw, and ISO images are supported.
 
 :::
 
-![](/img/v1.2/upload-image-local.png)
+![](/img/v1.3/image-hv/upload-image-local.png)
 
 
 #### HTTP 413 Error in Rancher Multi-Cluster Management
@@ -175,4 +175,4 @@ You can add labels to the image, which will help identify the OS type more accur
 
 If your image name or URL contains any valid information, the UI will automatically recognize the OS type and image category for you. If not, you can also manually specify those corresponding labels on the UI.
 
-![](/img/v1.2/image-labels.png)
+![](/img/v1.3/image-hv/image-labels.png)