Skip to content

Commit 53e00f6

Browse files
committed
add additionalImages step
1 parent 302149d commit 53e00f6

File tree

1 file changed

+16
-1
lines changed

1 file changed

+16
-1
lines changed

docs/vendor/embedded-disaster-recovery.mdx

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -126,9 +126,24 @@ To configure Velero Backup and Restore custom resources for Embedded Cluster dis
126126
```
127127
For more information about how to rewrite image names using the 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, including additional examples, see [Task 1: Rewrite Image Names](helm-native-v2-using#rewrite-image-names) in _Configuring the HelmChart v2 Custom Resource_.
128128

129+
1. If you support air gap installations, add any images that are referenced in your Backup and Restore resources to the `additionalImages` field of the KOTS Application custom resource. This ensures that the images are included in the air gap bundle for the release so they can be used during the backup and restore process in environments with limited or no outbound internet access. For more information, see [additionalImages](/reference/custom-resource-application#additionalimages) in _Application_.
130+
131+
**Example:**
132+
133+
```yaml
134+
apiVersion: kots.io/v1beta1
135+
kind: Application
136+
metadata:
137+
name: my-app
138+
spec:
139+
additionalImages:
140+
- elasticsearch:7.6.0
141+
- quay.io/orgname/private-image:v1.2.3
142+
```
143+
129144
1. (Optional) Use Velero functionality like [backup](https://velero.io/docs/main/backup-hooks/) and [restore](https://velero.io/docs/main/restore-hooks/) hooks to customize the backup and restore process as needed.
130145

131-
**Example**:
146+
**Example:**
132147

133148
For example, a Postgres database might be backed up using pg_dump to extract the database into a file as part of a backup hook. It can then be restored using the file in a restore hook:
134149

0 commit comments

Comments
 (0)