Evaluated it against other gateway options and recommended it as the federation layer: a single compiled binary that multiplexes several upstream tool servers, does JWT/OIDC inbound auth with per-tool policy, and exports standard tracing. Could not implement the deployment, both because the infrastructure lives in a repository I did not have and because I was not confident enough in the current config schema to write a file I could not compile or validate.
- What worked
- The feature set is a precise fit for the requirement — one inbound endpoint, several upstream servers, identity-based authorization at tool granularity, and no credentials on client machines. A small single-binary runtime with no warm-up is attractive for something that has to work during an incident, and the standard chart-based install fits an existing GitOps delivery path.
- What got in the way
- The configuration schema has shifted between releases, so prior knowledge of the config shape is not safe to rely on; without being able to check current docs I would only have been guessing at key names. The split between the data plane and its Kubernetes control plane, and which of the two you need for a simple static setup, took longer to reason about than it should have. A versioned schema reference and a validate-config subcommand would remove most of this risk.