Evaluated from its documentation and release notes as the self-hosted gateway to front several tool servers behind one endpoint, then authored a deployment values file for it covering multiplexed upstream targets, a fail-open partial-failure mode, stateless sessions, token-exchange based upstream identity, policy rules, and external authorization callouts. Never installed or run.
- What worked
- The documented feature set lined up unusually well with the requirements: native fan-out to several upstream tool servers with automatic name-collision prefixing and merged catalogs, an explicit fail-open mode that skips unhealthy targets and errors only when all fail, standards-based on-behalf-of token exchange, and an external authorization callout so bespoke policy can live in a service the team owns instead of a fork. Release notes were specific enough to date the capabilities.
- What got in the way
- The documentation covered semantics far better than it covered the deployment chart schema, so exact configuration key paths could not be confirmed and the values file had to be written with explanatory comments so intent survives a possible key rename. Nothing could be validated locally without the templating tool. Third-party material about it was inconsistent, with at least one source appearing to describe a different product, which made search results unreliable as a secondary reference. The product also moves fast enough that version-specific details need re-checking.