Custom Installations
There are various cookbooks available to install paymentHub on kubernates cluster.
Rolling your own helm chart
The best approach would be to take one of the tested Lab Environment examples from below and start customizing it to the actual requirements. Once the configuration looks proper, proceed with the deployment as detailed above. Note that very specific charts are in env-labs and generic/ use-case charts are in env-templates.
Some basic information for payment hub helm charts:
ph-ee-env-templates:
ph-ee-env-template is the parent chart used for the deployment of various paymentHub services. This chart contains the default configuration for every service. In paymentHub this chart is termed as ph-ee-engine.
ph-ee-env-templates cookbooks:
g2p-sandbox
identity-account-mapper
ph-ee-env-labs:
ph-ee-env-labs is the chart repository used to alter the default configuration of the ph-ee-engine(ph-ee-env-templates) chart. This repository contains various cookbooks as per the user's requirement.
ph-ee-env-labs cookbooks:
ph-ee-fin-back-end
ph-ee-fin-front-end
operations
How to install cookbooks:
Your current directory should be in ph-ee-env-labs/ ph-ee-env-templates depending on which chart you're installing.
ph-ee-fin-back-end installation:
Steps to install ph-ee-fin-back-end chart:
Build the chart dependency:
Install the helm chart:
Enter appropriate RELEASE_NAME and YOUR_NAMESPACE in the above command.
Install the elastic secrets required for the services:
Install the kibana secrets:
Now you are good to go with ph-ee-fin-back-end chart.
ph-ee-fin-front-end installation:
Steps to install ph-ee-fin-front-end chart:
Build the chart dependency:
Install the helm chart:
Ways to connect to External RDBMS:
To use the external RDBMS service for any of the cookbooks just need to follow below steps:
Here is an example of ph-ee-fin-back-end chart.
Open values.yaml of ph-ee-fin-back-end chart in an editor.
Replace HOST_NAME, USER, and PASSWORD with your external RDBMS hostname, user, and password.
Replace all the other occurrence of datasource with the external RDBMS details. e.g: importer_rdbms, messagegateway, etc.
Last updated