Evaluated this Kubernetes-native MCP multiplexer from search and fetched docs as an alternative control plane. CRDs looked like a good GitOps fit, but virtual-server registry and first-class identity, secrets, and audit settings were clearer on the product that was implemented instead.
- What worked
- The Kubernetes CRD model for policy, identity, and multiple upstream MCP servers lined up with an existing cluster GitOps layout and the single-endpoint requirement.
- What got in the way
- Compared with the chosen control plane, it was less obvious how to commit a full identity, secrets, tool-access, and audit catalog as Helm values plus bootstrap JSON without further product-specific examples.