Files
vault/Career/Tech Talks/OpenShift migration Tech Talk.md
Zaine 129ce1442b
Some checks failed
Build Quartz Notes / build (push) Failing after 20s
13
2026-07-13 09:16:09 +01:00

23 lines
1.3 KiB
Markdown
Executable File

---
note type:
- microlise
- note
date: 2026-07-02
done: true
---
**OpenShift migration**
- PROD workloads are going to be migrated from Sovereign House (PROD) to Powergate (GEN) clusters
- `mms. Local` is going to eventually be dropped
- OpenShift needs to use `*.ml.local` for ALL routes, which map directly to the routes (on HELM charts)
- `api.microlise.com` ->`apim.ml.local`
- `api-oat.microlise.com` -> `oat.apim.ml.local` (same for `cert`/ `uat`)
- `apim-int.ml.local` replaces `svc.cluster.local` for internal communications (`dev.apim-int.ml.local` for DEV)
- `live.microlise.com` -> `app.ml.local` / `api.ml.local` (same for oat/cert/uat)
- `apim` or `live` using paths - continue with paths for routes - otherwise use subdomains
- route migration - add new route, alongside old, test, drop the old route (once everything has been updated to point to it)
- need to use `route` `name` in the HELM charts
- new subdomains - use the new workflow in #help-openshift-platform once it's available - automated process
- setup the new routes on GEN/DEV first, to confirm they're all working - then repeat on PROD
- workload migration - process TBC - spin up new PROD workloads on GEN cluster, drop from PROD cluster
- GEN - doesn't require change control, PROD workloads on GEN - will still require it