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

Caller-identity probe: name railiance01 as target and require node check
Some checks failed
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Has been cancelled
Details

Browse source 
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 58902@bnt-lap001
Assistant-Session: 7ac7f865-2dc5-4aa7-8eb7-27a342109c2f
This commit is contained in:
tegwick 2026-09-22 16:19:28 +02:00
parent f68da93083
commit eaf0af617c
1 changed files with 7 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/flex-auth-caller-identity.md
View file

@ -54,6 +54,13 @@ Do not re-run these against `warn`: step 2 would return a decision.
recorded run used Python. The bash shape below is the contract, not the recorded run used Python. The bash shape below is the contract, not the
exact live invocation. exact live invocation.
The target cluster is railiance01 (node `92.205.62.239`). Run the commands
on the node (`ssh railiance01`, then the commands below). If you run them
from the workstation, first confirm that `kubectl get nodes -o wide` shows
that IP. A kubeconfig pointing at the retired coulombcore cluster answers
with the wrong cluster (see
`the-custodian/docs/agent-environment-orientation.md` §1).
```bash ```bash
POD=$(kubectl -n user-engine get pod -l app.kubernetes.io/name=user-engine \ POD=$(kubectl -n user-engine get pod -l app.kubernetes.io/name=user-engine \
-o jsonpath='{.items[0].metadata.name}') -o jsonpath='{.items[0].metadata.name}')