NCP-AI Nutanix Certified Professional - Artificial Intelligence v6.10

Comprehensive and Detailed Explanation From Exact Extract of Nutanix Artificial Intelligence documents knowledge without any external URL or links:

According to the Nutanix Enterprise AI network requirements and installation guide, the administrator must configure a fully qualified domain name (FQDN) on the DNS domain that resolves to the external IP address of the Ingress Gateway service.1 In the architecture used by Nutanix Enterprise AI (which typically leverages the KServe stack), Istio provides the Ingress Gateway (often referred to as the Envoy Ingress Gateway or Istio Ingress Gateway).2

The documentation explicitly states: "Ensure that you configure a fully qualified domain name (FQDN) on the DNS domain that is accessible to your Kubernetes cluster using the external IP address of the Envoy Ingress Gateway service ." 3 Since Envoy acts as the data plane and ingress controller for the Istio service mesh in this deployment, the DNS record must point to the LoadBalancer IP allocated to the Istio/Envoy gateway to route traffic correctly to the AI endpoints.

Comprehensive and Detailed Explanation From Exact Extract of Nutanix Artificial Intelligence documents knowledge without any external URL or links:

According to the Nutanix Enterprise AI documentation regarding "Viewing Sample API Code," the sample code provided by the dashboard is designed to help developers integrate the endpoint into their applications. The documentation explicitly states: "The sample code contains the URL and API key required to access the endpoint."

These two components are essential for the client application to locate the service (Endpoint URL) and authenticate the request (API Key). User credentials (such as username/password) are not part of the standard inference API request, and infrastructure details like GPU type are abstracted away from the client code.