Skip to content

Commit 302149d

Browse files
committed
rm sentence about deploy failure
1 parent c9ad715 commit 302149d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/vendor/embedded-disaster-recovery.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ To configure Velero Backup and Restore custom resources for Embedded Cluster dis
9595
- '*'
9696
```
9797

98-
1. For any image names that you include in your Backup and Restore resources, rewrite the image name using the Replicated KOTS [HasLocalRegistry](/reference/template-functions-config-context#haslocalregistry), [LocalRegistryHost](/reference/template-functions-config-context#localregistryhost), and [LocalRegistryNamespace](/reference/template-functions-config-context#localregistrynamespace) template functions. This ensures that the image name is rendered correctly during deployment, allowing the image to be pulled from the user's local image registry (such as in air gap installations) or through the Replicated proxy registry. If any images referenced in Backup and Restore resources cannot be pulled, the application will fail to deploy after a restore.
98+
1. For any image names that you include in your Backup and Restore resources, rewrite the image name using the Replicated KOTS [HasLocalRegistry](/reference/template-functions-config-context#haslocalregistry), [LocalRegistryHost](/reference/template-functions-config-context#localregistryhost), and [LocalRegistryNamespace](/reference/template-functions-config-context#localregistrynamespace) template functions. This ensures that the image name is rendered correctly during deployment, allowing the image to be pulled from the user's local image registry (such as in air gap installations) or through the Replicated proxy registry.
9999

100100
**Example:**
101101

0 commit comments

Comments
 (0)