ircs-prod-config/README.md

ircs-prod-config

Independent GitOps repository for IRCS V3 production namespace ircs-prod.

This repo intentionally separates production runtime state from the source repository:

• source repo: gitea-admin/ircs-project-v3, builds and pushes service images.
• GitOps repo: gitea-admin/ircs-prod-config, declares Kubernetes runtime resources.

Secrets are not stored here. Run scripts/prepare-prod-secrets.ps1 before syncing the core ArgoCD application.

Deployment order:

1. Prepare ircs-prod namespace and secrets.
2. Apply apps/ircs-prod-core-application.yaml to ArgoCD and sync it.
3. Let the V3 migrator initialize a clean database. Do not migrate legacy ircs-system data by default.
4. Verify portals and BFF through cluster endpoints.
5. Sync apps/ircs-prod-edge-application.yaml or apply ircs-prod/edge-cutover, then remove old ircs-system business routes.

Edge cutover is isolated from core to avoid hostname conflict while the old ircs-system routes still own production domains.

Current cutover state:

• ircs-prod-core: Synced/Healthy.
• ircs-prod-edge: Synced/Healthy.
• ircs-system/huawai-route and ircs-system/ircs-route: removed.
• ircs-system/kibana-route: retained.