mirror of
https://github.com/bitnami/charts.git
synced 2026-04-02 07:17:26 +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
@@ -228,6 +228,10 @@ In order to make the chart follow standards and to ease the generation of this c
|
||||
|
||||
All the settings specified in the `hub.configuration` value are consumed by the `jupyter_config.py` script available in the [templates/hub/configmap.yaml](https://github.com/bitnami/charts/blob/main/bitnami/jupyterhub/templates/hub/configmap.yaml) file. This script can be changed by providing a custom ConfigMap via the `hub.existingConfigmap` value. The [official JupyterHub documentation](https://jupyterhub.readthedocs.io/en/stable/reference/config-examples.html) has more examples of the `jupyter_config.py` script.
|
||||
|
||||
### 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).
|
||||
|
||||
### Restrict traffic using NetworkPolicies
|
||||
|
||||
The Bitnami JupyterHub chart enables NetworkPolicies by default. This restricts the communication between the three main components: the Proxy, the Hub and the Single User instances. There are two elements that were left open on purpose:
|
||||
|
||||
Reference in New Issue
Block a user