feat(charts): add dentalemon-seeder Helm chart #1

jericho1050 · 2026-01-10T07:00:00Z

Summary

This PR adds the Helm chart and ArgoCD configuration for deploying the DENTALEMON demo data seeder. The seeder application code lives in monobase-mycure PR #35.

Why split across repos?

Following the team's convention:

Application code (TypeScript, generators, seeders) → monobase-mycure
K8s deployment (Helm charts, ArgoCD) → monobase-infra

What's included

charts/dentalemon-seeder/ - Helm chart with:

Kubernetes Job template for one-time seeding
ConfigMap for configuration (patient count, reset, dry-run)
ExternalSecret support for MongoDB URI
Resource limits and security context

argocd/applications/templates/dentalemon-seeder.yaml - ArgoCD app:

Sync wave 4 (runs after MongoDB and services are ready)
PostSync hook for automatic execution
Auto-sync with prune and self-heal

Usage

Enable in deployment values (e.g., values/deployments/mycure-staging.yaml):

dentalemon-seeder:
  enabled: true
  config:
    patientCount: "20"
    resetData: "false"
  externalSecrets:
    enabled: true
    secretStore: "gcp-secret-store"
    mongoUriKey: "mycure-staging-mongodb-uri"

Configuration Options

Value	Default	Description
`enabled`	`false`	Enable/disable the seeder
`config.patientCount`	`"20"`	Number of patients to generate
`config.resetData`	`"false"`	Clear existing demo data first
`config.dryRun`	`"false"`	Validate without changes
`config.demoOrgName`	`"Smile Bright Dental Clinic"`	Demo organization name

Test plan

Helm lint passes
Helm template renders correctly
Job deploys successfully in staging
Seeder completes without errors
Demo data visible in DENTALEMON app

Related: mycurelabs/monobase-mycure#20

🤖 Generated with Claude Code

Add Helm chart for deploying the DENTALEMON demo data seeder as a Kubernetes Job. This chart enables automated seeding of dental clinic demo data for testing and client demonstrations. ## What's included: - `charts/dentalemon-seeder/` - Helm chart with: - Job template for one-time seeding - ConfigMap for seeder configuration - ExternalSecret support for MongoDB URI - Configurable patient count, reset, dry-run options - `argocd/applications/templates/dentalemon-seeder.yaml` - ArgoCD app - Sync wave 4 (runs after services are deployed) - Auto-sync with prune and self-heal ## Usage: Enable in deployment values: ```yaml dentalemon-seeder: enabled: true config: patientCount: "20" resetData: "false" ``` Related to: mycurelabs/monobase-mycure#20 Co-Authored-By: Claude Opus 4.5 <[email protected]>

Copilot

Pull request overview

This PR adds infrastructure for deploying the DENTALEMON demo data seeder as a Kubernetes Job via Helm and ArgoCD. The PR also includes updates to the practice-staging deployment configuration, infrastructure settings (domain changes, cert-manager Gateway API support), bootstrap configurations (repository URL updates to a personal fork), and practice secret templates.

Changes:

Added dentalemon-seeder Helm chart with Job, ConfigMap, and ExternalSecret templates
Added ArgoCD application template for dentalemon-seeder with sync wave 4
Updated practice-staging deployment with new domain (mediqueue.online) and dentalemon app configuration
Updated infrastructure configuration with Gateway API support for cert-manager and new domain settings
Updated bootstrap configurations to use personal fork repository
Added practice deployment secrets templates

Reviewed changes

Copilot reviewed 16 out of 16 changed files in this pull request and generated 13 comments.

Show a summary per file

File	Description
charts/dentalemon-seeder/*	Complete Helm chart for demo data seeding job with security contexts, resource limits, and configuration management
argocd/applications/templates/dentalemon-seeder.yaml	ArgoCD application definition with PostSync hook for automatic seeder execution
values/deployments/practice-staging.yaml	New practice deployment configuration with complete stack (frontend, backend, database, storage)
values/infrastructure/main.yaml	Updated domain to mediqueue.online and added Gateway API support for HTTP-01 challenges
infrastructure/secrets-template/*	Secret templates for practice deployment (MongoDB, MinIO, Cloudflare)
argocd/bootstrap/*	Updated repository URLs to personal fork (jericho1050)
argocd/infrastructure/templates/cert-manager.yaml	Added Gateway API experimental feature gate support

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-01-10T07:06:06Z

values/infrastructure/main.yaml

+        - api.stg       # api.stg.mediqueue.online (hapihub API)
+        - mail.stg      # mail.stg.mediqueue.online (mailpit)
+        - storage.stg   # storage.stg.mediqueue.online (minio)
        - storage.stg


Duplicate subdomain entry 'storage.stg' appears on line 97 and 98. This redundancy should be removed to keep the configuration clean.

Suggested change

- storage.stg

Copilot · 2026-01-10T07:06:06Z

values/deployments/practice-staging.yaml

+    sectionName: http
+
+  config:
+    API_URL: "https://api-stg.mediqueue.online"
+    HAPIHUB_URL: "https://api-stg.mediqueue.online"


Configuration inconsistency: The gateway.sectionName is set to 'http' (line 263), but the API_URL and HAPIHUB_URL are configured with 'https://' protocol (lines 266-267). This mismatch is consistent with the other services in this file and needs to be corrected.

Copilot · 2026-01-10T07:06:07Z

infrastructure/secrets-template/practice-secrets.yaml

+  mongodb-root-password: "practice-mongo-password-123"
+  # Replica set key (must be at least 6 characters)
+  mongodb-replica-set-key: "practice-replica-key-secret-12345"
+
+---
+# MinIO Secret
+apiVersion: v1
+kind: Secret
+metadata:
+  name: minio
+  namespace: practice-staging
+type: Opaque
+stringData:
+  # MinIO root credentials
+  root-user: "minio-admin"
+  root-password: "practice-minio-password-123"


Weak passwords used in practice secrets file. The passwords 'practice-mongo-password-123' and 'practice-minio-password-123' are predictable and not secure. While this is marked as practice/development only, consider using stronger examples to encourage better security practices, even in development environments.

Copilot · 2026-01-10T07:06:07Z

infrastructure/secrets-template/practice-secrets.yaml

+# - Use strong, randomly generated passwords
+#
+# Usage:
+# 1. Create the namespace first: kubectl create namespace practice-staging


Namespace mismatch in documentation: The usage instructions reference 'practice-staging' namespace (line 12), but the actual deployment configuration uses 'mediqueue-staging'. This inconsistency will confuse users following the instructions.

Copilot · 2026-01-10T07:06:07Z

charts/dentalemon-seeder/values.yaml

+image:
+  repository: ghcr.io/mycurelabs/dentalemon-seeder
+  pullPolicy: Always
+  tag: "latest"


The image tag is set to 'latest' with pullPolicy 'Always'. While this is acceptable for development, it's not a best practice as 'latest' tags can lead to unpredictable deployments and make rollbacks difficult. Consider using semantic versioning or commit SHAs for better deployment tracking and reproducibility.

Suggested change

tag: "latest"

tag: "1.0.0"

Copilot · 2026-01-10T07:06:08Z

values/deployments/practice-staging.yaml

+    sectionName: http  # Use HTTP listener
+    timeouts:
+      request: "60s"
+
+  livenessProbe:
+    enabled: true
+
+  readinessProbe:
+    enabled: true
+
+  podDisruptionBudget:
+    enabled: false
+
+  autoscaling:
+    enabled: false
+
+  # External Secrets disabled for practice
+  # Enable this in production to sync secrets from cloud KMS
+  externalSecrets:
+    enabled: false
+
+  # Environment variables for HapiHub
+  env:
+    - name: PUBLIC_URL
+      value: "https://api-stg.mediqueue.online"
+    - name: APP_URL
+      value: "https://api-stg.mediqueue.online"


Configuration inconsistency: The gateway.sectionName is set to 'http' (line 98), but the environment variables PUBLIC_URL and APP_URL are configured with 'https://' protocol (lines 122, 124). This mismatch could cause connectivity issues or unexpected behavior.

Copilot · 2026-01-10T07:06:08Z

infrastructure/secrets-template/practice-secrets.yaml

+  namespace: practice-staging
+type: Opaque
+stringData:
+  # Root password for MongoDB
+  mongodb-root-password: "practice-mongo-password-123"
+  # Replica set key (must be at least 6 characters)
+  mongodb-replica-set-key: "practice-replica-key-secret-12345"
+
+---
+# MinIO Secret
+apiVersion: v1
+kind: Secret
+metadata:
+  name: minio
+  namespace: practice-staging


Namespace mismatch: The secrets are configured for 'practice-staging' namespace (lines 23, 37), but the deployment configuration uses 'mediqueue-staging' namespace (practice-staging.yaml line 22). This will cause the secrets to be unavailable to the application pods.

Copilot · 2026-01-10T07:06:09Z

argocd/applications/templates/dentalemon-seeder.yaml

+  source:
+    path: charts/dentalemon-seeder
+    repoURL: {{ .Values.argocd.repoURL }}
+    targetRevision: {{ .Values.argocd.targetRevision | default "main" }}


The targetRevision defaults to 'main' (line 20), but the infrastructure-root.yaml and applicationset-auto-discover.yaml use 'HEAD' as the targetRevision. This inconsistency could lead to confusion. Consider using 'HEAD' for consistency across all ArgoCD configurations, or document why different revisions are used.

Suggested change

targetRevision: {{ .Values.argocd.targetRevision | default "main" }}

targetRevision: {{ .Values.argocd.targetRevision | default "HEAD" }}

Copilot · 2026-01-10T07:06:09Z

charts/dentalemon-seeder/templates/NOTES.txt

+Demo users created (password: demo123):
+  - [email protected] (Dentist/Admin)
+  - [email protected] (Dentist)
+  - [email protected] (Orthodontist)
+  - [email protected] (Dental Assistant)
+  - [email protected] (Receptionist)
+  - [email protected] (Admin)


The NOTES.txt hardcodes demo user credentials (password: demo123) and email addresses (lines 16-22). This information might be better suited for documentation rather than deployment notes, as it could expose sensitive information if these credentials are used in any real environment, even staging. Consider removing or conditionally displaying this based on environment type.

Suggested change

Demo users created (password: demo123):

- [email protected] (Dentist/Admin)

- [email protected] (Dentist)

- [email protected] (Orthodontist)

- [email protected] (Dental Assistant)

- [email protected] (Receptionist)

- [email protected] (Admin)

Demo users have been created for common roles (e.g., Dentist, Orthodontist, Assistant, Receptionist, Admin).

Refer to the project documentation or your environment's configuration for details on demo accounts and credentials.

Copilot · 2026-01-10T07:06:09Z

charts/dentalemon-seeder/Chart.yaml

+apiVersion: v2
+name: dentalemon-seeder
+description: Demo data seeder for DENTALEMON dental clinic management application
+type: application
+version: 1.0.0
+appVersion: "1.0.0"
+keywords:
+  - dentalemon
+  - seeder
+  - demo-data
+  - dental
+home: https://github.com/mycurelabs/monobase-infra
+sources:
+  - https://github.com/mycurelabs/monobase-mycure
+maintainers:
+  - name: MYCURE Inc.
+    email: [email protected]


Missing README.md file for the dentalemon-seeder chart. Other charts in the repository (e.g., charts/dentalemon) include README.md files with usage instructions, configuration examples, and documentation. Adding a README would help users understand how to configure and use the seeder.

jericho1050 and others added 12 commits December 25, 2025 21:42

initial setup for proactice

746ef0e

fix: remove nodePool selector for DOKS compatibility

e3519a8

fix: use full hostnames for HTTPRoutes

e7e9b0d

fix: update gateway domain to mediqueue.online

3f2d043

fix: point infrastructure to user fork

41c9c91

fix: configure HTTP-01 challenge for Let's Encrypt certificates

1f5a424

fix: use real email for Let's Encrypt registration

9abfe87

feat: enable Gateway API support in cert-manager for HTTP-01 challenges

5873ff1

fix: use extraArgs for Gateway API feature gate

caecd13

fix: use first-level subdomains for free Cloudflare SSL

5afad72

feat: enable dentalemon app for practice staging

f724b8e

Copilot AI review requested due to automatic review settings January 10, 2026 07:00

Copilot started reviewing on behalf of jericho1050 January 10, 2026 07:00 View session

Copilot AI reviewed Jan 10, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat(charts): add dentalemon-seeder Helm chart #1

feat(charts): add dentalemon-seeder Helm chart #1

Uh oh!

jericho1050 commented Jan 10, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Jan 10, 2026

Uh oh!

Copilot AI Jan 10, 2026

Uh oh!

Copilot AI Jan 10, 2026

Uh oh!

Copilot AI Jan 10, 2026

Uh oh!

Copilot AI Jan 10, 2026

Uh oh!

Copilot AI Jan 10, 2026

Uh oh!

Copilot AI Jan 10, 2026

Uh oh!

Copilot AI Jan 10, 2026

Uh oh!

Copilot AI Jan 10, 2026

Uh oh!

Copilot AI Jan 10, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

	targetRevision: {{ .Values.argocd.targetRevision \| default "main" }}
	targetRevision: {{ .Values.argocd.targetRevision \| default "HEAD" }}

feat(charts): add dentalemon-seeder Helm chart #1

Are you sure you want to change the base?

feat(charts): add dentalemon-seeder Helm chart #1

Uh oh!

Conversation

jericho1050 commented Jan 10, 2026

Summary

Why split across repos?

What's included

Usage

Configuration Options

Test plan

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Jan 10, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 10, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 10, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 10, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 10, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 10, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 10, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 10, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 10, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 10, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant