trade-next/trade-docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(migration): record sol k3s bootstrap and host service access

Browse Source
This commit is contained in:
u1
2026-04-12 14:17:42 +00:00
parent bf1a1e2e2d
commit f2f97d1d5a
1 changed files with 10 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
doc/migration-todo.md
View File

@@ -269,10 +269,16 @@ Date: `2026-04-12`
### 17. Install and bootstrap `k3s` on `mevnode`
- Pending.
- Done on `2026-04-12`.
- Define the target `k3s` installation model on `mevnode`.
- Define the target storage class, host paths, and bootstrap dependencies needed before application rollout.
- Verify that the base cluster, registry access, namespaces, and secret distribution work before any application components are installed.
- Done on `2026-04-12`: installed single-node `k3s` on `sol` as `v1.34.6+k3s1`.
- Done on `2026-04-12`: installed `k3s` in a minimal profile with `traefik`, `servicelb`, `local-storage`, and `network-policy` disabled.
- Done on `2026-04-12`: validated core addons on `sol`; both `coredns` and `metrics-server` are healthy.
- Done on `2026-04-12`: prepared shared namespace `trade-infra` with `ClusterIP` services `postgres-host` and `redis-host` backed by host `EndpointSlice` targets on `149.50.96.162`.
- Done on `2026-04-12`: opened `ufw` access on `cni0` only for pod CIDR `10.42.0.0/24` to `6443`, `10250`, `5432`, and `6379`.
- Done on `2026-04-12`: validated `pod -> service -> host` connectivity from a test pod to both `Postgres` and `Redis`.
### 18. Install `Postgres` and `Redis` on `mevnode`
@@ -281,8 +287,9 @@ Date: `2026-04-12`
- Validate persistence, storage placement, service discovery, restart behavior, and cold start.
- Validate that `Postgres` lands on the dedicated `1 TiB` trade storage area and that `Redis` lands on its separate small quota before application rollout.
- Do not install application components until `Postgres` and `Redis` are healthy.
- Done on `2026-04-12`: `Postgres` and `Redis` are running on `sol` as host services, both bound to `127.0.0.1` at this stage.
- Done on `2026-04-12`: `Postgres` and `Redis` are running on `sol` as host services, bound to `127.0.0.1` and `149.50.96.162` for `k3s` pod access.
- Done on `2026-04-12`: validated `Postgres` on `/srv/trade/postgres/16/main`, validated `Redis` on `/srv/trade/redis`, and confirmed `btrfs` quotas are active for both paths.
- Done on `2026-04-12`: `Postgres` listens with pod CIDR access in `pg_hba.conf`, and `Redis` announces `149.50.96.162` for cluster-aware clients inside `k3s`.
### 19. Prepare a minimal canary namespace for trade on `mevnode`
@@ -324,7 +331,7 @@ Date: `2026-04-12`
- [ ] 14. Define CPU and memory reservations that protect `agave-validator`.
- [ ] 15. Define the minimum safe free RAM headroom on `mevnode` during rollout.
- [ ] 16. Define the maximum acceptable swap usage on `mevnode` during rollout.
- [ ] 17. Install and bootstrap `k3s` on `mevnode`.
- [x] 17. Install and bootstrap `k3s` on `mevnode`.
- [x] 18. Install `Postgres` and `Redis` on `mevnode`.
- [ ] 19. Prepare a minimal canary namespace for trade on `mevnode`.
- [ ] 20. Bring up `Hasura`, API, and frontend on `mevnode`.