brhmshrnv/gitops

GitOps implementation with GitlabCI, ArgoCD and HELM

GitOps

GitOps implementation with GitlabCI, ArgoCD, Helm

Basic settings

• GitLab CI Pipeline
• Kubernetes template using Helm Charts
• Continuous Deployment using ArgoCD
• GitOps repository structure

Gitlab repository structure

Note

You can add variables in Gitlab at the group level from Settings -> CICD -> Variables

• CD_ARGOCD_URL: argocd.local.az
• CD_ARGOCD_USERNAME: argo
• CD_ARGOCD_PASSWORD: password
• CI_GITLAB_REGISTRY_URL: gitlab.local.az:4567
• CI_GITLAB_REGISTRY_USERNAME: admin_registry
• CI_GITLAB_REGISTRY_PASSWORD: password
• CI_GITLAB_USERNAME: admin_ci
• CI_GITLAB_PASSWORD: password
• CI_PROJECT_TEMPLATE: cicd/demo/ci-template
• CD_GITLAB_PROJECT: cicd
• EXPO_USERNAME: expo
• EXPO_PASSWORD: passowrd

The following stages are for the backend, frontend and mobile.

stages:

• package
• image_build
• push_to_helm
• argocd_sync
• deploy_to_expo

The package stage is undergoing the build operation. The image_build stage creates an image from Dockerfile. The push_to_helm stage writes a new image tag id to the helm repo. The argocd_sync stage synchronizes the application in argpcd due to a change in the helm repo. The deploy_to_expo stage for mobile includes build operations for both android and ios.

Requirements

• Gitlab
• ArgoCD
• Helm
• Expo account

Author Information

Samir Nabadov