|
Deployment of backend modules to specified Kubernetes namespace where an Okapi and Postgresql instances are already available. There is the question of how DB data will be handled on iterative builds. List of backend modules deployed derived from okapi-install.json which would reside in platform-core snapshot branch.
Deployment consists of the following tasks:
- pull MDs from folio-registry
- Post deployment descriptor to local instance of Okapi.
- Ansible role with deployment and service templates.
- DB info in pre-installed K8s secrets
- Secure supertenant. Does supertenant require it's own designated deployment of mod-perms, mod-auth, mod-login, and mod-users? Seems a bit much.
Tenant configuration:
- Configuration of a 'default' tenant and the loading of reference and sample data and additional configuration.
|
|
Implemented with Terraform and Helm.
First, all core backend modules have `Helm chart.
All core modules deploying into the Project by Terraform to Rancher Application (Folio Helm repository).
Default source for images - DockerHub/folioci.
Helm has postinstall-hook and upgrade-hook to install module decriptor, module deployment, tenant creation and registration.
|