CI/CD with Argo Workflows

Laminar uses Argo Workflows for building container images and ArgoCD for GitOps-based deployments.

Architecture

GitHub Repositories
    │
    ├─ laminar (Rust backend)
    ├─ laminar-frontend (Console + Product)
    └─ laminar-infra (Infrastructure)
         │
         ▼
   Argo Workflows (Manual Triggers)
    │
    ├─ *-check: Lint, test
    └─ *-build: Build → Push to ECR
         │
         ▼
   ECR Registry
    │
    ├─ laminar/backend
    ├─ laminar/backend-deps
    ├─ laminar/console
    └─ laminar/product
         │
         ▼
   ArgoCD (Pull-based Sync)
    │
    └─ Helm Charts → EKS Cluster

ECR Registry

All images are pushed to AWS ECR:

792306802931.dkr.ecr.us-east-1.amazonaws.com/laminar/
├── backend          # Rust engine
├── backend-deps     # Engine dependencies layer
├── console          # Console UI
└── product          # Product site

Image Tagging Strategy

Branch names with / are converted to - (e.g., feature/auth → feature-auth).

Workflow Templates

All workflows run in the argo namespace using a DAG (Directed Acyclic Graph) structure.

Build Workflows

Check Workflows

Workflow Parameters

Running Workflows

Via Argo CLI

# Submit with default parameters
argo submit -n argo --from workflowtemplate/console-build
 
# Submit with custom branch
argo submit -n argo --from workflowtemplate/console-build \
  -p revision=feature/new-dashboard
 
# Submit engine build with specific deps image
argo submit -n argo --from workflowtemplate/engine-build \
  -p revision=master \
  -p deps-image-tag=a1b2c3d
 
# Watch workflow progress
argo watch -n argo @latest
 
# List workflows
argo list -n argo
 
# Get logs
argo logs -n argo <workflow-name>
 
# Resubmit failed workflow
argo resubmit -n argo <workflow-name>

Via Argo Workflows UI

1. Access the UI at https://ci.lmnr.cloud

2. Click Workflow Templates in the left sidebar

3. Select the desired template (e.g., console-build)

4. Click + Submit

5. Override parameters if needed:

   • revision: Enter branch name (e.g., feature/new-feature)

6. Click Submit

7. Monitor progress in the workflow view

Post-Build Deployment

After building an image, update the deployment:

Option 1: Update Values File (Recommended)

Edit the image tag in the appropriate values file and commit:

# For console
vim k8s/laminar-product/values-eks.yaml
# Update: console.image.tag: "new-tag"
 
# Commit and push
git add . && git commit -m "Update console image tag" && git push

ArgoCD will automatically sync the change.

Option 2: ArgoCD CLI Override

# Sync with image override
argocd app set laminar-product \
  --helm-set console.image.tag=a1b2c3d
 
argocd app sync laminar-product

Option 3: kubectl (Quick Testing)

# Direct image update
kubectl set image deployment/console \
  console=792306802931.dkr.ecr.us-east-1.amazonaws.com/laminar/console:a1b2c3d \
  -n laminar-product

Directory Structure

laminar-infra/
├── argo-workflows/
│   ├── Taskfile.yml
│   └── workflows/
│       ├── engine-build.yaml
│       ├── engine-check.yaml
│       ├── engine-deps-build.yaml
│       ├── console-build.yaml
│       ├── console-check.yaml
│       ├── product-build.yaml
│       └── product-check.yaml
├── argocd/
│   ├── Taskfile.yml
│   ├── projects/
│   │   └── laminar.yaml
│   └── applications/
│       ├── laminar-product.yaml
│       ├── laminar-monitoring.yaml
│       └── ...
└── k8s/
    └── laminar-cicd/
        ├── Chart.yaml
        ├── Taskfile.yml
        ├── values.yaml
        └── values-eks.yaml