mirror of
https://github.com/bitnami/charts.git
synced 2026-03-29 16:27:11 +08:00
[bitnami/*] docs: 📝 Add "Backup & Restore" section (#30711)
* [bitnami/*] docs: 📝 Add "Backup & Restore" section Signed-off-by: Javier J. Salmerón García <javier.salmeron@broadcom.com> * docs: 📝 Add missing charts Signed-off-by: Javier J. Salmerón García <javier.salmeron@broadcom.com> * docs: 🚨 Fix lint issues Signed-off-by: Javier J. Salmerón García <javier.salmeron@broadcom.com> * docs: 🚨 Fix lint issues Signed-off-by: Javier J. Salmerón García <javier.salmeron@broadcom.com> --------- Signed-off-by: Javier J. Salmerón García <javier.salmeron@broadcom.com>
This commit is contained in:
committed by
GitHub
parent
56812f8671
commit
35ab536374
@@ -155,6 +155,10 @@ This chart allows you to set your custom affinity using the `XXX.affinity` param
|
||||
|
||||
As an alternative, you can use of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `XXX.podAffinityPreset`, `XXX.podAntiAffinityPreset`, or `XXX.nodeAffinityPreset` parameters.
|
||||
|
||||
### Backup and restore
|
||||
|
||||
To back up and restore Helm chart deployments on Kubernetes, you need to back up the persistent volumes from the source deployment and attach them to a new deployment using [Velero](https://velero.io/), a Kubernetes backup/restore tool. Find the instructions for using Velero in [this guide](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-backup-restore-deployments-velero-index.html).
|
||||
|
||||
## Persistence
|
||||
|
||||
The [Bitnami MongoDB®](https://github.com/bitnami/containers/tree/main/bitnami/mongodb-sharded) image stores the MongoDB® data and configurations at the `/bitnami/mongodb` path of the container.
|
||||
|
||||
Reference in New Issue
Block a user