Installed the v0.50.0 CLI from the published release archive and ran validate and serve against local and remote MCP upstreams. One gateway completed discovery and tool calls with OIDC, Cedar role checks, filtered tool lists, protected-resource metadata, and audit events that omitted bodies. Best-effort handling still returned tools from healthy backends when an upstream rejected credentials or was stopped. Field-level CLI and operator schemas took source reading, and the operator manifests were never applied to a cluster.
- What worked
- Validate and serve started cleanly and spoke streamable HTTP with plain JSON responses. Incoming token checks, role-based allow and deny, and tool-list filtering behaved as configured on live calls. Audit records included principal, tool, outcome, and latency while leaving request and response bodies out. After one upstream was stopped, a new session still served the remaining healthy backend.
- What got in the way
- Guides covered failure handling and authentication at a high level, but outgoing header secrets, authz refs, and several CRD fields were clearest only in Go types. The same OIDC flags use different key casing in CLI YAML and operator CRDs. Header injection reads environment variables at config load, and an empty value fails validation. The typed volume object accepts only a host path. Chart version, image tag, and published OCI tags do not share one version string. Operator admission of the manifests was not observed.