coulomb/railiance-platform
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

RPF-WP-0064-T10: bridge status takes no tunnel argument
Some checks failed
CI Smoke / host-smoke (push) Waiting to run
Details
CI Smoke / container-smoke (push) Waiting to run
Details
CCR intake gate / gate (push) Has been cancelled
Details

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 4515@bnt-lap001
Assistant-Session: 0bf96127-6e04-41be-bfda-d11717c3f354
This commit is contained in:
codex 2026-10-28 00:59:41 +01:00
parent f00298cd44
commit 86c92792b2
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
workplans/RPF-WP-0064-isolated-original-openbao-restore.md
View file

@ -787,7 +787,7 @@ a tunnel, so the port-forward maps the break-glass listener 8210 to 18210 and th
production.
```bash
bridge status k3s-api-railiance01 # up; restore with: bridge up k3s-api-railiance01
bridge status | grep k3s-api-railiance01 # up; restore with: bridge up k3s-api-railiance01
export KUBECONFIG=~/.kube/config-railiance01
kubectl -n openbao get pod openbao-0 -o wide
kubectl -n openbao exec openbao-0 -- bao status -format=json \