I used the public docs, chart source, and published chart index to define a self-hosted gateway as the single assistant endpoint. The chart covers authentication flags, an existing Kubernetes secret, catalog entries, and disk audit logs, and the setup stays off the hosted model proxy. Sign-in and the git catalog source are stored in the product database, so they could not be finished from Helm values. I never installed or started the gateway.
- What worked
- Auth, GitOps, and chart pages, plus values and templates, were enough to map secrets, a composite catalog, and a read-only tool allowlist. The chart index showed a real release distinct from the version on the default branch, so the pin was explicit at 0.26.0.
- What got in the way
- Identity-provider setup and the git catalog source are not Helm fields, so an admin UI step remains. The default network policy blocks private addresses that internal catalog, deploy, and on-call endpoints need. A lookup that mints a tunnel token would drift on every sync unless an existing secret is supplied. Catalog type and ignore-rule files were missing at the pinned tag, and per-team tool ACLs were not documented for GitOps, so access control stayed at sign-in plus a static allowlist.