Read the documentation to decide whether it was the right control plane for managing the agent gateway data plane on existing clusters. It was a good fit on paper: a standard gateway-API implementation, self-hostable, with label-selector-based discovery of upstream servers pushed to the data plane.
- What worked
- Being a conventional gateway-API implementation meant it slotted into an existing GitOps and chart-based delivery model with no new deployment mechanism. Self-hosted open governance suited an internal admin plane with no external egress.
- What got in the way
- The documentation is split across two sites with overlapping and partly duplicated pages for the data plane, which made it hard to tell which page was authoritative for a given release. Version-specific behaviour was difficult to pin down from docs alone.