public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-28 05:59:03 +00:00
Code Issues Packages Projects Releases Wiki Activity

Document how to prevent naming conflict with restore resource

Browse Source
This commit is contained in:
Catherine Luse
2021-02-26 09:56:35 -07:00
parent 5d0d6495ce
commit ff2c089876
2 changed files with 14 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.5/en/backups/restoring-rancher/_index.md
+7 -1
View File
@@ -48,9 +48,15 @@ A restore is performed by creating a Restore custom resource.
2. Cluster-scoped resources 2. Cluster-scoped resources
3. Namespaced resources 3. Namespaced resources
### Logs
To check how the restore is progressing, you can check the logs of the operator. Follow these steps to get the logs: To check how the restore is progressing, you can check the logs of the operator. Follow these steps to get the logs:
```yaml ```yaml
kubectl get pods -n cattle-resources-system kubectl get pods -n cattle-resources-system
kubectl logs <pod name from above command> -n cattle-resources-system -f kubectl logs <pod name from above command> -n cattle-resources-system -f
``` ```
### Cleanup
If you created the restore resource with kubectl, remove the resource to prevent a naming conflict with future restores.
content/rancher/v2.x/en/backups/v2.5/restoring-rancher/_index.md
+7 -1
View File
@@ -48,9 +48,15 @@ A restore is performed by creating a Restore custom resource.
2. Cluster-scoped resources 2. Cluster-scoped resources
3. Namespaced resources 3. Namespaced resources
### Logs
To check how the restore is progressing, you can check the logs of the operator. Follow these steps to get the logs: To check how the restore is progressing, you can check the logs of the operator. Follow these steps to get the logs:
```yaml ```yaml
kubectl get pods -n cattle-resources-system kubectl get pods -n cattle-resources-system
kubectl logs <pod name from above command> -n cattle-resources-system -f kubectl logs <pod name from above command> -n cattle-resources-system -f
``` ```
### Cleanup
If you created the restore resource with kubectl, remove the resource to prevent a naming conflict with future restores.