coulomb/rein-aharness
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat: k8s:// ClusterIP claim env + complete payload target_repo

Browse source 
Resolve llm-connect / actcore-api / edge-relay without port-forward.
Include target_repo on FI and Binky complete payloads for ops UI artefacts.
This commit is contained in:
tegwick 2026-08-05 17:23:03 +02:00
parent 6383944939
commit 94a15d67aa
7 changed files with 207 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

19
docs/ops-run-claim-loop.md
View file

@ -101,7 +101,24 @@ systemctl --user enable --now rein-aharness-claim-loop.service
journalctl --user -u rein-aharness-claim-loop -f
```
Port-forward if claim-loop runs on host and API is ClusterIP-only:
### Host access to cluster services (no port-forward)
On railiance01 (single-node k3s), set **k8s://** pseudo-URLs in
`claim-loop.env` (see `deploy/systemd/claim-loop.env.example`). The
`~/bin/rein-aharness-claim` wrapper resolves them to Service ClusterIPs at
start. Canon: activity-core `docs/llm-connect-host-access.md`.
```bash
# migrate existing env
./deploy/scripts/refresh-claim-loop-k8s-urls.sh
# reinstall wrapper
./deploy/scripts/install-claim-loop-user.sh
systemctl --user restart rein-aharness-claim-loop.service
```
**Deprecated:** long-lived `kubectl port-forward` to 127.0.0.1:8010 / :8080.
Legacy note (break-glass only) if ClusterIP routing is broken:
```bash
kubectl -n activity-core port-forward svc/actcore-api 8010:8010