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 theEnvoy Ingress Gateway service."3Since Envoy acts as the data plane and ingress controller for theIstioservice 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:

To install Nutanix Enterprise AI (NAI), specifically when pulling the required container images and Helm charts from the Nutanix repository, authentication is required.2

Access Token Source:The administrator must log in to theNutanix Portal(specifically the Software Downloads or Licenses section) to generate or retrieve theAccess Token(often referred to as the API Key for the registry).3

Usage:This token is then used as the DOCKER_API_KEY or password in the Helm install command (helm install ... --set imagePullSecret.password=...) to authenticate against the ntnx-charts or specific container registry.

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

TheView Sample Request(or "View Sample Code") feature in the Endpoint Details or List view is designed to facilitate immediate connectivity for developers.

Content:Clicking this link opens a dialog that displays a code snippet (formatted for cURL, Python, etc.) containing exactly two critical pieces of information: theEndpoint URLand the associatedAPI Keyrequired to authenticate against that endpoint.

Purpose:This allows administrators or developers to copy a ready-made command that verifies connectivity without having to manually construct the URL or hunt for the API key in a separate menu.

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

The Nutanix Enterprise AI (NAI) dashboard and API endpoints are exposed to the external network via an Ingress Gateway. In the NAI architecture on Kubernetes, Istio (specifically the Envoy Ingress Gateway service) is the component responsible for managing this ingress traffic.

If the NAI dashboard URL is inaccessible, it indicates a failure in the ingress layer where traffic is not being correctly routed to the nai-ui service. Troubleshooting steps for this issue involve checking the status of theIstioingress gateway service (e.g., nai-ingress-gateway in the envoy-gateway-system or nai-system namespace) to ensure it is running and has successfully claimed an external IP address. While MetalLB provides the IP address, Istio handles the actual HTTP/S routing and termination; therefore, an inaccessibility issue is most directly linked to the Istio service configuration or health.

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

To successfully configure a custom domain with a corporate CA-signed certificate in Nutanix Enterprise AI, the administrator must ensure the following two external prerequisites are met:

DNS Configuration (Option A):AnA recordmust be created in the corporate DNS server that points the fully qualified domain name (FQDN) ai.company.com to the external IP address assigned to the NAI Ingress Gateway (LoadBalancer IP). This ensures that traffic destined for the custom URL reaches the cluster.

Certificate Provisioning (Option C):A validCA-signed TLS certificate(and its corresponding private key) matching the FQDN ai.company.com must be obtained from the corporate Certificate Authority. This certificate is then stored as a Kubernetes Secret (e.g., nai-letsencrypt-certificate or similar custom secret) and referenced by the Ingress Gateway to enable secure HTTPS termination.

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

Nutanix Enterprise AI licensing is based on resource consumption metrics, specificallyvCPUandGPU GB.

Mandatory License:The documentation states: "Youmust have a vCPU licenseto create an inference endpoint". This is the base requirement for the software to function and manage deployments.

Optional License:TheGPU GBlicense is described as "optional and only required for GPU-based endpoints".

Enforcement:The system enforces this by preventing the creation ofanyinference endpoint if the vCPU license has expired. If both licenses expire, existing endpoints are hibernated. Therefore, the vCPU license is the fundamental prerequisite for endpoint creation capability.

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

The Nutanix Enterprise AI licensing model enforces strict behavior upon license expiration.

Hibernation Trigger:According to the licensing documentation, while the expiry of a vCPU license prevents the creation ofnewendpoints, it allows existing ones to remain active. However, the system is programmed tohibernate all endpoints(both GPU and non-GPU) specificallyafter both the vCPU and GPU GB licenses expire.

Diagnosis:Since "all current endpoints" are hibernated and there are no operational errors (anomalous events) in the audit logs, the cause is the enforcement of the license expiration policy.