Multi-Deployment Support for K8 Deployment

The Multi-Deployment support allows the multiple deployments of K8 instances, which otherwise could have blocked the performance of some of the existing instances running. In other words, multi-deployment support in K8 enables the execution of multiple API and Database Pods independently.

To achieve this, prefix the environment name variable to the existing pod names in the appropriate name space. Using the environment variable set, the pods initialize and execute with the modified name.
Following are the steps to use the Multi-Deployment feature:

1. Navigate to the Consent Helm Package folder.
   
2. Open the create_namespace.bat / create_namespace.sh script and specify the name spaces used during K8 deployment.
   
3. Open the required start-up script (start-savingspot-mongo.bat / start-savingspot-mongo.sh) for deployment and set the ENV_NAME property as the environment name for multi-deployment.
   
4. Similarly, edit the name space names in the start-up script (start_consent-mssql.bat / start_consent-mssql.sh).
   
5. Execute the start-up script (start-savingspot-mongo.bat / start-savingspot-mongo.sh) to start the deployment activity.
6. After the deployment, to view the name space changes, execute the command kubectl get all -n <namespace> to list down all the resources present in the name space.
   
   In the above image, its confirm that the environment name "Stage" is added to the pods and services name. Hence, the APIs can be triggered and evaluated.

   Following is APIs URL structure,
   Base Path: ttp://<IP_ADDRESS>:<PORT>/<context-root>/api/<version>/
   For Example: http://localhost:9500/ms-savingspot-api/api/v1.0.0/
   The resource path of the endpoint can be found in the swagger document.
   A sample endpoint of a Savings Pot can be http://localhost:9500/ms-savingspot-api/api/v1.0.0/holdings/savingPots