titan/atlas-iac
3
0
Fork 0
Code Issues Pull Requests 9 Actions Packages Projects Releases Wiki Activity

docs: record Claude 5.5 deployment checks

Browse Source
This commit is contained in:
jenkins 2026-09-29 15:53:45 -05:00
parent 206c61993d
commit bb4c0b6951
1 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/hermes_suite_claude55.md
View File

@ -106,5 +106,21 @@ dry-run passed; Flux diff was limited to the planner Deployment and ConfigMap.
The documented combined server-side/client dry-run flags are incompatible with
the installed kubectl, so the client dry-run was run without `--server-side`.
## Deployment verification
Flux applied `206c61993d1ff50ed64ab61164b9eee8cd183b45`, and the new worker
reports CLI `2.1.285`. In-cluster application HTTP checks returned authenticated
health/capabilities/preflight 200, invalid-token 401, management-path 404, and
local-only preflight 422 without selecting an external provider. Preflight pins
`claude-opus-5-5`; capabilities expose all three server configuration choices.
These checks used loopback HTTP with the approved client forwarding address and
do not establish end-to-end LAN HTTPS connectivity.
The operator host is currently on `192.168.1.64`; direct TLS-verified connection
to `192.168.22.50:443` timed out before HTTP. No LAN routing, access restrictions,
TLS configuration, ingress paths, or client URL were changed to work around that
host limitation. The existing client endpoint remains
`https://worker.bstein.dev/suite-planning`.
Official references: [model configuration](https://code.claude.com/docs/en/model-config)
and [CLI settings](https://code.claude.com/docs/en/settings-reference).