admin/ircs-prod-config
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record clean prod cutover

Browse Source
This commit is contained in:
Prodiglagla
2026-06-14 16:04:38 +08:00
parent 59b93e9f78
commit fc7f421203
2 changed files with 10 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitignore
+1
View File
@@ -0,0 +1 @@
backups/
README.md
+9 -2
View File
@@ -13,8 +13,15 @@ Deployment order:
1. Prepare `ircs-prod` namespace and secrets. 1. Prepare `ircs-prod` namespace and secrets.
2. Apply `apps/ircs-prod-core-application.yaml` to ArgoCD and sync it. 2. Apply `apps/ircs-prod-core-application.yaml` to ArgoCD and sync it.
3. Run V3 migrator and compatible data migration from `ircs-system`. 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. 4. Verify portals and BFF through cluster endpoints.
5. Sync or apply `ircs-prod/edge-cutover` and remove old `ircs-system` routes. 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. 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.