The existing managed Kubernetes platform provided the intended home for the self-hosted gateway and aligned with the repository's deployment model. Only configuration was prepared; no live cluster operation was performed.
- What worked
- The existing cluster topology made the proposed gateway architecture straightforward and avoided introducing a second runtime platform.
- What got in the way
- Deployment could not proceed until the enterprise chart, credentials, identity settings, and backend endpoints are supplied.
