GPU deep dives:
  - "What is the GPU temperature and power draw right now?"
  - "Show me tensor core activity and memory bandwidth utilization on the GPU"
  - "What are the SM and memory clock speeds — is the GPU throttling?"
  - "How much VRAM is used vs free on each GPU?"
  - "Show me PCIe throughput on the GPU node"

Validation output are inline after the curl cmds

Start Praxis and a dummy endpoint:

cargo run -p praxis -- -c examples/configs/operations/admin-interface.yaml
python3 -m http.server 3000 both running.

  ### 1. Build Praxis with JSON-RPC Filter
  ```bash
  cargo build --release -p praxis

 2. Use Simple netcat Backend

The ExternalModel reconciler creates an HTTPRoute with a RequestHeaderModifier filter that sets Host: <provider-endpoint> (e.g., Host: api.openai.com). This filter was questioned during PR #709 review — could BBR handle this instead, since BBR already handles path rewriting and API key injection?

We investigated whether the filter could be moved into BBR's ext-proc pipeline so that all request mutations happen in a single place.

• OpenShift cluster with oc/kubectl access as cluster-admin
• MaaS repo cloned (e.g., ~/istio-gw/prs/4-rconciler-namespace-path/models-as-a-service)

#!/bin/bash
GW_HOST=$(kubectl get gateway maas-default-gateway -n openshift-ingress -o jsonpath='{.spec.listeners[0].hostname}')
TOKEN=$(oc whoami -t)

echo "Gateway: $GW_HOST"
echo ""

PR #709 - re-validation and updated as of 4/11 12:06AM EST

$ HOST="https://maas.$(kubectl get ingress.config.openshift.io/cluster -o jsonpath='{.spec.domain}')"
  TOKEN=$(oc whoami -t)

$ API_KEY=$(curl -sSk -X POST "$HOST/maas-api/v1/api-keys" \
    -H "Authorization: Bearer $TOKEN" \

• Anthropic multi-turn validation (the errors at turn 8 are TRLP and expected as part of the test)

HOST="https://maas.$(kubectl get ingress.config.openshift.io/cluster -o jsonpath='{.spec.domain}')"
TOKEN=$(oc whoami -t)

$ ./scripts/deploy.sh --operator-type odh
[INFO] ===================================================
[INFO]   Models-as-a-Service Deployment
[INFO] ===================================================
[INFO] Validating configuration...
[INFO] Configuration validated successfully

Breakage when deploying MaaS with: ./scripts/deploy.sh --operator-type odh

maas-api pods crash with CrashLoopBackOff because the opendatahub:maas-api service account lacks:

1. Permission to read the maas-db-config secret in opendatahub namespace
2. Permission to list maasmodelrefs and maassubscriptions CRDs