Skip to content

Docs: add AuthBridge two-hop egress-control demo (Kind + OCP)#108

Merged
pdettori merged 1 commit into
kagenti:mainfrom
pdettori:docs/authbridge-egress-demo
Jul 14, 2026
Merged

Docs: add AuthBridge two-hop egress-control demo (Kind + OCP)#108
pdettori merged 1 commit into
kagenti:mainfrom
pdettori:docs/authbridge-egress-demo

Conversation

@pdettori

Copy link
Copy Markdown
Member

What

Adds deploy/knative/README-authbridge.md — a demo doc for the RC1 AuthBridge (Rosso Cortex) two-hop egress-control path, covering both Kind and OpenShift. Cross-linked from the Smoke test sections of README-kind.md and README-ocp.md.

Why

The runnable proof already existed (leaf-smoke.sh on Kind, rc1-ocp-gate.sh on OCP), but nothing documented it: README-kind.md/README-ocp.md don't mention SH_AUTHBRIDGE, and serverless-harness-demo.md covers only scale-to-zero/sessions. A newcomer had no walkthrough of how Cortex egress works or how to see it.

Contents

  • The two hops — Profile A shared LLM gateway (AB1) + Profile B per-sandbox forward-proxy (AB2); the control-before-inject invariant.
  • Quick start, both platforms:
    • Kind: SH_AUTHBRIDGE=1 ./setup-kind.shLEAF_LIVE_SMOKE=1 SH_AUTHBRIDGE=1 NS=default bash leaf-smoke.sh
    • OpenShift: SH_AUTHBRIDGE=1 ./setup-ocp.sh./rc1-ocp-gate.sh gate (up→smoke→restore; RC1_GATE_KEEP=1 to keep applied)
  • What it installs (AB1/AB2/ibac-stub/echo-target/secrets/tightened egress), the six capability claims with their PASS messages, and manual secret-free / allow / deny checks (spec §5, exact kubectl commands).
  • Troubleshooting (incl. the OVN-K DNS 5353 fix Harness egress NetworkPolicy blocks DNS on OVN-Kubernetes (harness cannot resolve any host) #102 and the relay tsx fix) and cleanup/restore.

Verification

  • OCP flow live-verified on 4.20 (gate 6/6, 16/16) — Route, secret names/keys, and env values (ECHO_CRED=PLACEHOLDER-TOKEN, ANTHROPIC_BASE_URL=http://authbridge-ab1:8080) confirmed against the live cluster and manifests.
  • Kind commands sourced from setup-kind.sh / leaf-smoke.sh (the RC1-1/RC1-2 Kind gates passed 13/13 and 16/16).
  • All 14 cross-linked paths confirmed to exist.

Docs only. Follows the existing README section/table/# => conventions.

Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com>

There was no demo doc for the RC1 AuthBridge/Cortex egress-control path: the
runnable proof (leaf-smoke.sh on Kind, rc1-ocp-gate.sh on OCP) existed, but
nothing walked a reader through the two-hop topology, how to enable it, or how to
see credential injection + allow/deny control. README-kind.md/README-ocp.md don't
mention SH_AUTHBRIDGE at all; serverless-harness-demo.md covers only scale-to-zero.

Add deploy/knative/README-authbridge.md covering BOTH platforms:
- the two hops (Profile A shared LLM gateway AB1; Profile B per-sandbox forward-proxy
  AB2) and the control-before-inject invariant;
- Quick start for Kind (SH_AUTHBRIDGE=1 setup-kind.sh + leaf-smoke.sh) and OpenShift
  (SH_AUTHBRIDGE=1 setup-ocp.sh + rc1-ocp-gate.sh gate);
- what it installs (AB1/AB2/ibac-stub/echo-target/secrets/tightened egress), the six
  capability claims with their PASS messages, and manual secret-free / allow / deny
  checks (spec §5, exact kubectl commands);
- troubleshooting (incl. the OVN-K DNS 5353 fix kagenti#102 and the relay tsx fix) and
  cleanup/restore.

Cross-linked from the Smoke test sections of README-kind.md and README-ocp.md.

OCP flow live-verified on 4.20 (gate 6/6, 16/16); Kind commands are from
setup-kind.sh/leaf-smoke.sh (the RC1-1/RC1-2 Kind gates: 13/13, 16/16).

Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com>
Signed-off-by: Paolo Dettori <dettori@us.ibm.com>
@pdettori pdettori merged commit a66b425 into kagenti:main Jul 14, 2026
10 checks passed
@pdettori pdettori deleted the docs/authbridge-egress-demo branch July 14, 2026 15:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Harness egress NetworkPolicy blocks DNS on OVN-Kubernetes (harness cannot resolve any host)

1 participant