Deployment
CI/CD pipeline and deployment processes for the Wealthy platform
Deployment Guide

This section covers the complete deployment pipeline and processes used to deploy services to the Wealthy platform.
Overview
The Wealthy platform uses a modern CI/CD pipeline with the following key components:
- Source Control: GitHub with fork-based development
- Build System: AWS CodeBuild for container builds
- Container Registry: AWS ECR (Elastic Container Registry)
- Deployment: ArgoCD for GitOps-based Kubernetes deployments
- Runtime: Google Kubernetes Engine (GKE)
Deployment Flow
Each developer follows this standardized process:
- Fork & Pull Request: Developer forks the main repository and creates a PR
- Code Review: PR undergoes review and testing
- Merge: Once approved, PR is merged to master branch
- Build Trigger: Developer triggers deployment in AWS
- Container Build: AWS CodeBuild creates Docker image from master branch
- Registry Push: Built image is pushed to AWS ECR
- GitOps Deployment: ArgoCD detects ECR push and deploys to GKE
Key Features
- Container-based: All services run in Docker containers
- GitOps: Declarative deployment management
- Multi-environment: Support for dev, staging, and production
- Rollback Capability: Easy rollback to previous versions
Helm Chart Repository
All deployment configurations, Helm charts, and Kubernetes manifests are centrally managed in the dedicated repository:
- Repository: https://github.com/wealthy/helm-chart-repository/
- Purpose: Contains all deployment Helm charts and configuration settings
- Access: Contact
mahesh@wealthy.infor repository access - Usage: Used by ArgoCD for GitOps-based deployments to Kubernetes clusters
This repository serves as the single source of truth for all deployment configurations across development, staging, and production environments.