Skip to content

Commit 7758c42

Browse files
committed
docs(kubernetes): use explicit Velero restore name in backup guide
Address review feedback from coderabbitai on content/en/docs/next/kubernetes/backups-with-velero-addon.md:158-161: without an explicit restore name, `velero restore create --from-backup demo-1` auto-generates `demo-1-<timestamp>`, so `velero restore describe demo-1` would fail. Pass `demo-1-restore` as the explicit restore name on both commands. Signed-off-by: Andrey Kolkov <androndo@gmail.com>
1 parent ed95568 commit 7758c42

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

content/en/docs/next/kubernetes/backups-with-velero-addon.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -155,9 +155,9 @@ Simulate a loss by deleting the namespace, then restore it from the backup:
155155

156156
```bash
157157
kubectl delete namespace demo
158-
velero -n cozy-velero restore create \
158+
velero -n cozy-velero restore create demo-1-restore \
159159
--from-backup demo-1
160-
velero -n cozy-velero restore describe demo-1 --details
160+
velero -n cozy-velero restore describe demo-1-restore --details
161161
```
162162

163163
When the restore reaches `Phase: Completed`, the namespace and its objects are recreated. Verify:

0 commit comments

Comments
 (0)