From 86c92792b295a3959bdfb6db8cdfa46d455134a3 Mon Sep 17 00:00:00 2001 From: codex Date: Wed, 28 Oct 2026 00:59:41 +0100 Subject: [PATCH] RPF-WP-0064-T10: bridge status takes no tunnel argument Co-Authored-By: Claude Opus 5.5 Assistant: claude-code Assistant-Model: opus Assistant-Process: 4515@bnt-lap001 Assistant-Session: 0bf96127-6e04-41be-bfda-d11717c3f354 --- workplans/RPF-WP-0064-isolated-original-openbao-restore.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/workplans/RPF-WP-0064-isolated-original-openbao-restore.md b/workplans/RPF-WP-0064-isolated-original-openbao-restore.md index 335e938..f570b61 100644 --- a/workplans/RPF-WP-0064-isolated-original-openbao-restore.md +++ b/workplans/RPF-WP-0064-isolated-original-openbao-restore.md @@ -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 \