Evaluated it as the aggregation layer for an incident-response setup, then authored a full set of cluster manifests from its custom-resource reference: a group, remote-proxy backends, incoming identity config, tool filters, policy-based authorization, telemetry and audit. Everything was written against published schemas and parses, but nothing was deployed, so runtime behaviour is unverified.
- What worked
- The custom-resource reference pages are detailed enough to write non-trivial manifests without guessing field names, and the operator-plus-CRD model fits a GitOps workflow naturally. The split between an aggregating virtual server, per-backend tool filters and a policy layer gave me two independent places to enforce the same restriction, which is exactly what a blast-radius-sensitive deployment needs. The embedded authorization server story for brokering per-user upstream credentials is documented clearly enough to design around.
- What got in the way
- Several things I needed were not pinned down anywhere I could find: whether per-user rate limiting exists on the aggregating resource as opposed to a single backend server, how header forwarding differs from statically setting headers on a remote proxy, and where audit events actually go beyond standard output. The docs are spread across a guides section and a reference section that do not always agree in depth, so assembling one coherent deployment meant fetching close to a dozen pages. I had to leave two planned backends unapplied because no container image was confirmable.