nGene

Description

/TODO/

/TODO/

The team responsible for maintaining and troubleshooting the application.

Main Point of Contact:

The repository for the application can be found at GitHub Link.

It has two environments, one for development and one for production; details are as follows:

	Development	Production
git branch	develop	`release/*`
Deployment environment	Cluster: `ace-test` Namespace: `ngene-dev`	Cluster: `ace-prod` Namespace: `gcs-ace-de-ngene`
Deployment tool	argocd-test/api.ngene.dev.gred.ai argocd-test/dashboard.ngene.dev.gred.ai argocd-test/appvs.ngene.dev.gred.ai	argocd-prod/api.ngene.gred.ai
URL	- http://ngene.dev.gred.ai/ - Accessible only via VPN - Authentication via Okta	- http://ngene.gred.ai/ - Accessible only via VPN - Authentication via Okta
Infra resources	- RDS: ace-de-dev-pg - Neptune: /TODO/	- RDS: ace-de-prod-pg
Service Account	IRSA: irsa.ace-test.ngene-dev.api	IRSA: irsa.ace-prod.gcs-ace-de-ngene.api

The Terraform workspace for the infrastructure can be found at Terraform Workspace Link.

EKS Service account -> IRSA IAM Role -> The role has the inline policy that allows access to the dataset buckets

This represents the branching of the nGene repository.

[develop]---------+------ (development)
|                 |
+--- feature/* ---+
|
+--- release/*----------- (production)

If there is a ‘fix’, ‘feat’, or ‘hotfix’ present in the git commit, the GitHub action release will bump up the version. So it’s automatically.

You should manually update the helm verion in Chart.yaml.

Monitoring Dashboard: Grafana
- Metrics being monitored: Memory usage by pod, CPU usage by pod, Replica Availability, PV Capacity
Logging Dashboard: Logs are available on the same Grafana Dashboard.
- To search logs in more details, please log in to OpenSearch > EKS ACE Test - Applications Dashboard > then choose namespace ngene-dev