Chose this as the control plane after reading project and Helm-chart docs, then wrote identity, secrets, tool-access, audit, catalog, and bootstrap config so one virtual server could front two upstream MCP servers. Never installed or ran a live gateway.
- What worked
- Docs described a registry-plus-proxy model with virtual servers, identity propagation, encrypted secrets, RBAC, and audit settings that mapped directly onto the one-endpoint and production-policy requirements. Chart values and REST registration were enough to draft a GitOps overlay without a live account.
- What got in the way
- Helm key placement was easy to get wrong: auth, SSO, and bootstrap roles belonged under secret rather than config, and the chart had no extra volume mounts for a roles file. RBAC permission names needed extra searching, and the registration script needed rework for existing virtual servers and heredoc invocation.