Shared Single Instance
...
This setup leverages kubernetes namespace in order to support multiple bahmni instances on the shared infrastructure where every instance have their own Database. This is still single tenant but provides more opportunities to optimize cost by sharing resources. This is more ideal for setting up smaller hospitals or polyclinics in a given geography cluster. Note: scale up and down would impact all the instances. We leveraged this setup to support various development environments on shared infra such as dev, qa, demo etc.
...
This setup is very similar to above except it also allows allocating dedicated infrastructure resources to one or more instances. This gives more control to scale up or down one or more bahmni instances based on the needs. This may be ideal for supporting bigger facilities into their own nodegroup within a given geography cluster to allow independent scale. We (e.g. we leveraged this setup to isolate our performance test environment from other development environments).
Multiple Bahmni Instance (in multiple nodegroups)
Each instance with their own Database (shared RDS across nodegroups)
multiple node group
1 - * Nodes (depending on the scale) independently managed in various nodegorups
Setup
Infra
Follow the setup guide to provision the infrastructure. Take a note while creating the resources to decide on what configuration you would want to support - specifically for the nodegroups. For example if you want to configure one shared nodegorup (FOO) with 2 bahmni instances and another dedicated nodegroup (BAR) for single bahmni instance you would have two folders under /terraforms/nodegroups. For reference see nonprod
...
Bahmni uses Helm Umbrella Chart (Chart of Charts) strategy to deploy Kubernetes cluster. There arent very many great resources to understand umbrella charts but you can refer this document to get the gist of how the charts are assembled using umbrella charts for Bahmni.
...