{"resourceId":"nvidia-nvke-preview-status-known-limitations","versions":[{"version":"external-486effaa2bfb8c9aa1b959e4a66eec85a66cccf679a32a141646a9e32ae879ca","resource":{"id":"nvidia-nvke-preview-status-known-limitations","title":"NVIDIA Kubernetes Engine (NVKE) preview documentation: supported features and known limitations, including plain-HTTP API, no authorization, and no management-plane backup or upgrade","organization":"NVIDIA","sector":"AI infrastructure / Kubernetes platform software","geography":"Global (operator-installed on own NVIDIA GPU infrastructure)","publishedAt":"Undated documentation page; NVKE preview surfaced publicly Nov 6–7, 2026 per independent reporting","publicationDate":null,"eventDate":null,"sourceName":"NVIDIA Kubernetes Engine documentation","sourceLabel":"NVIDIA docs (vendor documentation)","sourceUrl":"https://docs.nvidia.com/nvke/documentation/overview/preview-status-and-known-limitations","evidenceClass":"vendor-claim","outcomeClass":"emerging","topics":["infrastructure","data-security","operating-model"],"finding":"NVIDIA's NVKE documentation describes an open-source preview management system that lets an AI-factory operator create isolated Kubernetes workload clusters (own control plane, etcd, node pools) on its own GPU bare metal through NVIDIA Infra Controller (NICo). The known-limitations page states NVKE is not recommended for production; the API serves plain HTTP on port 30080 with authentication off after install; NVKE does no authorization, so any admitted caller can create or delete every workload cluster; customers receive only a non-revocable admin kubeconfig; and the management cluster has no self-management, upgrade, or backup/restore procedure.","sledRelevance":"Limited and indirect today. State shared-services centers, statewide research-computing consortia and large campus AI factories that hand out GPU clusters to agencies or departments are the closest SLED analogue to the 'operator with customers' NVKE targets. The vendor's own limitations list makes NVKE an evaluation item, not a deployable multi-tenant service, for public-sector environments in 2026.","evidence":"Vendor documentation read in full on the limitations page: supported-at-preview list (node OS images, nvkectl bootstrap, NICo provisioning, JWT authentication, OVN-Kubernetes, optional etcd encryption, node-pool scaling, NKTP telemetry, mock-NICo local quickstart) and known limitations for the management cluster, API/access, node pools, artifacts and telemetry. No performance or deployment metrics are reported.","architectureImplications":"Requires a dedicated management cluster (TPM nodes, SPIRE CA supplied by the operator), NICo or LaunchLayer as infrastructure provider, operator-built node images and registries, and an operator-supplied TLS endpoint in front of the API. GPU drivers and device plugins are handled outside NVKE (GPU Operator, per independent reporting).","governanceImplications":"Because NVKE does no authorization and admin kubeconfigs cannot be revoked until certificate expiry, any SLED pilot must restrict token issuance to staff allowed to manage every tenant cluster and record kubeconfig hand-offs as privileged-credential events.","securityPrivacyImplications":"Default plain-HTTP, unauthenticated API; tokens cross the network unencrypted without an operator TLS proxy; no per-user customer credentials; non-revocable admin kubeconfigs; the etcd encryption key file from bootstrap is the only off-node copy and must be stored securely.","caveats":"Vendor documentation for a preview; behavior and APIs may change. Page is undated, so the publication date is left null. No measured outcomes, customer deployments or U.S. public-sector use are described.","streamIds":["nvidia"],"roles":{"sales":"Frame NVKE as a roadmap signal, not a product to sell into SLED this quarter. NVIDIA is building an EKS-style managed Kubernetes layer for operators who run GPU clusters for customers, which maps loosely to state shared-services and statewide research-computing consortia. Its own limitations page says it is not for production. Use it to ask how those operators hand out isolated GPU clusters today and what tenancy controls they need, and avoid implying a supported multi-tenant service exists.","engineering":"Treat NVKE as a lab evaluation. The preview needs a TPM-backed management cluster, an operator SPIRE CA, NICo or LaunchLayer provisioning, and your own TLS front end because the API is plain HTTP with authentication off after install. There is no authorization layer, no management-plane upgrade or backup path, and customer access is a non-revocable admin kubeconfig. Compare against existing Cluster API, vCluster or managed-service patterns before any architecture commitment.","delivery":"Any pilot belongs in an isolated lab owned by the platform engineering team, run on the mock-NICo quickstart or spare bare metal. Document how the API is fenced, who holds tokens, and where the bootstrap kubeconfig and etcd key are stored. Define exit criteria up front: no tenant data, no production workloads, and a written gap list against the agency's security baseline before anyone proposes moving beyond preview."},"roleDetails":{"sales":{"customerProblem":"Operators of shared GPU estates need a repeatable way to give each department or agency its own isolated Kubernetes cluster.","stakeholders":["State shared-services or central IT platform lead","Research computing director","CISO / security architecture","Enterprise architecture"],"discoveryQuestions":["How do you provision isolated GPU clusters for tenants today?","Which tenancy, credential-revocation and audit controls are mandatory?","Are you pursuing any NVIDIA Cloud Partner-style operating model?"],"valueHypothesis":"If NVKE matures past preview, it could reduce custom tooling for multi-tenant GPU cluster provisioning on NVIDIA bare metal; today the value is an informed roadmap comparison.","potentialEngagement":"Short tenancy-architecture review comparing current cluster provisioning with NVKE preview capabilities and gaps.","unsupportedClaims":["Production readiness","Built-in role-based authorization","Any public-sector deployment","Cost or staffing savings"]},"engineering":{"fit":"Only operators running many customer clusters on NVIDIA bare metal managed through NICo; weak fit for single-team clusters.","architectureIntegration":"Management cluster runs NVKE management plane and CAPNICo; workload clusters provisioned via NICo with OVN-Kubernetes networking and SPIFFE/SPIRE node attestation.","prerequisites":["TPM 2.0 management nodes in odd counts","Operator-supplied SPIRE CA","NICo or LaunchLayer provider","Operator TLS endpoint and JWT identity provider"],"constraints":["Not recommended for production","No authorization layer","No management-plane upgrade or backup/restore","Admin kubeconfigs cannot be revoked"],"security":"API is plain HTTP with authentication off after install; must be network-fenced, TLS-fronted and JWT-protected before any caller is admitted.","proofOfValue":["Stand up mock-NICo quickstart and document every hardening step","Verify API is unreachable without TLS and JWT","Test kubeconfig hand-off and credential lifetime against policy"]},"delivery":{"work":"Lab evaluation of NVKE preview with a documented hardening and gap report.","dependencies":["Platform engineering capacity","Identity provider for JWT","Lab hardware or VM meeting quickstart specs"],"ownership":"Central platform engineering team, with security architecture sign-off.","skillsAdoption":"Requires Kubernetes, Cluster API, SPIFFE/SPIRE and OVN-Kubernetes skills; not an end-user capability.","governanceCheckpoints":["Security review before any network exposure","Credential-handling procedure for admin kubeconfigs","Exit decision before any tenant data"],"acceptanceCriteria":["Proposed: gap list mapped to agency security baseline completed","Proposed: API reachable only through TLS with JWT","Proposed: no production or tenant data used"],"risks":["Preview API changes","Unrecoverable management cluster without backup","Over-privileged tokens"]}},"retrievedAt":"2026-11-07T22:03:49-06:00","enrichedAt":"2026-11-07T22:03:49-06:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Operating NVKE requires specialized platform engineers; small SLED IT teams are unlikely to staff it during preview.","procurementImplications":"Do not cite NVKE as a supported managed-Kubernetes capability in RFP responses; ask vendors for production status, support terms and authorization model.","operatingModelImplications":"Fits a provider-to-tenant operating model (central IT serving agencies); requires credential lifecycle procedures NVKE itself does not supply.","sourceVerification":{"openedUrl":"https://docs.nvidia.com/nvke/documentation/overview/preview-status-and-known-limitations","referenceExcerpt":"NVKE does no authorization. Every caller that API authentication admits can call every endpoint, including the ones that create and delete workload clusters.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}