Phase 3: Gateway and Ingress
Phase 3: Gateway and Ingress
Phase 3: Gateway and Ingress
This phase installs the ingress layer that exposes NVCF services externally. It uses shared Gateway API infrastructure plus the NVCF Gateway Routes chart that creates HTTPRoutes and TCPRoutes for each service.
All core services from standalone-core-services must be running before proceeding. The Gateway Routes chart depends on the Notary Service and API Keys being available.
Complete Gateway quickstart before you install the Gateway Routes chart.
Keep these values from the Gateway quickstart:
You will use GATEWAY_ADDR in the Gateway Routes values and later connectivity
checks.
The Gateway Routes chart creates HTTPRoutes and TCPRoutes that connect external traffic to NVCF services through the Gateway.
Create gateway-routes-values.yaml (download template):
Replace <DOMAIN> with the GATEWAY_ADDR value obtained above.
For details on how routing works, verification commands, and production DNS/HTTPS setup, see gateway-routing.
The Admin Token Issuer Proxy was installed in standalone-core-services with
gateway.enabled: false because the Gateway CRDs did not yet exist. Now that the Gateway
is running, upgrade it to enable the admin endpoint HTTPRoute:
Verify the admin route was created:
With the gateway in place, verify the full stack is functional.
The backend value should match the cluster group name registered by the NVCA operator.
The instanceType and gpu values depend on the GPU types available in your cluster.
For invocation, the Host header uses wildcard subdomain routing:
<function-id>.invocation.<gateway-addr>.
For full HTTP invocation behavior, streaming, and errors, see
Generic HTTP Function Invocation.
To remove all gateway components:
Your NVCF control plane is now fully installed and accessible. Proceed to Self-Managed Clusters to install the NVCA Operator and connect your GPU nodes to the control plane.