We fixed a bug with the storage class. Now, you only need to ship the source package in a way Nebari can easily consume. The current strategy includes a helm chart for Kubernetes deployment and deployment within Nebari.

This might not be enough, as we still would require a terraform resource to create the necessary keycloak client with the proper rights over Nebari's realm.

Following tasks to be incldued in the helm chart:

• expected values
• configmaps for keycloak credentials and storage

public code repo https://github.com/nebari-dev/backup-restore

This will be shipped using dockerfile only as a container, and the pod spec will be present as a service within nebari, once its out of experimental, we can rethink the helm chart, as this requires maintainability of a helm index (simple to make, but extra work for now)