coulomb/llm-connect
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record railiance01 llm-connect smoke evidence
Some checks failed
CI / test (3.10) (push) Has been cancelled
Details
CI / test (3.11) (push) Has been cancelled
Details
CI / test (3.12) (push) Has been cancelled
Details

Browse Source 
Document the 2026-06-19 deployment and in-namespace fixture smoke on
railiance01, where activity-core runs. Clarify that the stable Service URL
is cluster-local and point scheduled triage evidence to ACTIVITY-WP-0010.
This commit is contained in:
Bernd Worsch
2026-06-19 15:58:04 +02:00
parent 92e55fde57
commit c0c9a3da1d
1 changed files with 14 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/activity-core-llm-endpoint.md
View File

@@ -111,5 +111,18 @@ handoff is verified as of 2026-06-18:
- The in-namespace smoke passed against the stable Service:
`smoke: pass health=ok latency_seconds=2.147 recommendations=1`.
2026-06-19 railiance01 recheck (activity-core production cluster):
- Deployed the `deploy/k8s/activity-core-llm-connect` overlay into the
`activity-core` namespace on `railiance01`, where the activity-core worker
runs. `coulombcore` retains a separate llm-connect instance for earlier
verification; consumers must call the Service in their own cluster.
- `activity-core/llm-connect-provider-secrets` reports `DATA 1`; no Secret
values were inspected or recorded.
- Restarted `deployment/actcore-worker` so pods consume
`LLM_CONNECT_URL=http://llm-connect.activity-core.svc.cluster.local:8080`.
- In-namespace fixture smoke on `railiance01` passed:
`smoke: pass health=ok latency_seconds=1.681 recommendations=1`.
Scheduled `daily_triage` evidence collection is activity-core ownership under
`ACTIVITY-WP-0006`.
`ACTIVITY-WP-0010`.