Initialize the Gateway

Scenario

After the first deployment, initialize ZStack API Router and verify that the database migration, service readiness, and console entry are available.

Prerequisites

  • zr-server is running.
  • PostgreSQL migration has been applied.
  • The administrator has a control-plane credential.
  • If the console is enabled, ZR_CONSOLE_DIST_DIR points to the console static directory.

Procedure

  1. Open the console URL, for example http://{ROUTER_HOST}:3080/ai-gateway.
  2. Log in with the administrator account or the platform-provided login method.
  3. Open System Status and verify that the service status is normal.
  4. Open Model Management, Channel Management, and Token Management to confirm that resource lists load correctly.
  5. Run health checks on the server:
curl -fsS http://{ROUTER_HOST}:3080/healthz
curl -fsS http://{ROUTER_HOST}:3080/readyz

Verification

CheckExpected Result
/healthzReturns success.
/readyzReturns ready.
ConsoleYou can log in and view resource lists.
OpenAPI/api/zr/openapi.json is accessible.

Notes

  • Do not use a test Cloud token in production.
  • If the console is unavailable but /readyz is normal, check the ingress proxy and static resource directory.
  • If /readyz is abnormal, check ZR_DATABASE_URL and database connectivity first.