Evaluated this as the multiplexing layer in front of several MCP servers, read its Kubernetes docs closely, and authored the full manifest set from them: gateway, label-selector MCP backend, route, JWT authentication policy and expression-based tool authorization. Never deployed it, so correctness of the manifests is unproven.
- What worked
- The capability set maps unusually well onto the requirement: one backend can multiplex many upstream MCP servers by label selector with configurable tool-name prefixing, token validation happens in the data plane where a client config cannot bypass it, and authorization is expressed over token claims. Being entirely declarative custom resources means it drops straight into a GitOps workflow with no second source of truth in an admin console. A machine-readable docs index helped me find pages quickly.
- What got in the way
- Documentation is versioned across parallel lines with different numbering, and it was not obvious which tree corresponds to the open-source release — I fetched the wrong version's page more than once. Several concrete fields I needed were never shown in a full example: the remote key-set configuration appears to reference a cluster service rather than an external host, so I had to assume an aliasing workaround; whether tool identity is available to policy expressions at backend scope was not documented; and forwarding behavior of validated claims to upstreams was unclear. I ended up shipping three explicitly flagged assumptions.