Deployment

Introduction

G1 CRM is deployed on Azure Kubernetes Cluster.

Environments

We currently host 3 environments of G1 CRM service.

If you want to access any of the namespaces, make sure you have successfully completed the local development.

Staging Environment

Inside your crm-services repository, run the following command to set the staging subscription on Azure.

make stage-aks

Now, set your local default namespace to stage-crm-services. And get the list of all pods running.

kubectl ns stage-crm-services
kubectl get pods

To check the log for any pod, you can run the following command

kubectl logs -f pod_name_you_selected_from_last_step

UAT Environment

For the UAT environment, we use the same staging clusters and subscription. Inside your crm-services repository, run the following command to set the uat subscription on Azure.

make stage-aks

Now, set your local default namespace to stage-crm-services. And get the list of all pods running.

kubectl ns uat-crm-services
kubectl get pods

To check the log for any pod, you can run the following command

kubectl logs -f pod_name_you_selected_from_last_step

Prod Environment

Inside your crm-services repository, run the following command to set the uat subscription on Azure.

make prod-aks

Now, set your local default namespace to stage-crm-services. And get the list of all pods running.

kubectl ns prod-crm-services
kubectl get pods

To check the log for any pod, you can run the following command

kubectl logs -f pod_name_you_selected_from_last_step

Deployment

We follow the following deployment matrix for G1 CRM services.