docs: record clean prod cutover
This commit is contained in:
@@ -13,8 +13,15 @@ Deployment order:
|
||||
|
||||
1. Prepare `ircs-prod` namespace and secrets.
|
||||
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.
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
Reference in New Issue
Block a user