站内导读
定位:NVKE 是 NVIDIA 提供的管理平面,平台团队装上它,就能在自有的 NVIDIA GPU 基础设施上为客户创建并运营托管 Kubernetes 集群。
核心能力
- 通过 NVKE API 或 nvkectl 申请集群,机器由 NICo 供给,每个工作负载集群带独立控制平面与 etcd。
- 节点加入前用 TPM 经 SPIFFE/SPIRE 完成证明,通过后才拿到加入凭据。
- 支持节点池的创建、扩缩与删除,也覆盖 Kubernetes 版本升级和节点替换。
- 本地快速入门在模拟机器上拉起开发用管理平面与一个工作负载集群,无需 NVIDIA 账号。
适用人群:适合自建 GPU 资源的平台团队;本地评估需 Linux 主机或虚拟机,6 CPU、12 GiB 内存、100 GiB 磁盘,装好 Docker 与虚拟 TPM;正式安装需接入 NICo。
位置づけ:NVKE は NVIDIA が提供する管理プレーンで、プラットフォームチームが導入すると、自前の NVIDIA GPU インフラ上で顧客向けのマネージド Kubernetes クラスタを作成・運用できます。
主な機能
- NVKE API または nvkectl でクラスタを申請し、マシンは NICo が供給します。各ワークロードクラスタには独立したコントロールプレーンと etcd が付きます。
- ノードは参加前に TPM を介した SPIFFE/SPIRE の検証を完了し、通過後に参加用の資格情報を受け取ります。
- ノードプールの作成、スケーリング、削除に対応し、Kubernetes のバージョンアップグレードやノード交換もカバーします。
- ローカルのクイックスタートでは、模擬マシン上に開発用の管理プレーンとワークロードクラスタを 1 つ立ち上げられ、NVIDIA アカウントは不要です。
対象ユーザー:自前で GPU リソースを持つプラットフォームチームに向いています。ローカル評価には Linux ホストまたは VM、6 CPU、12 GiB メモリ、100 GiB ディスク、Docker と仮想 TPM が必要で、本番導入には NICo への接続が必要です。
정의: NVKE는 NVIDIA가 제공하는 관리 플레인으로, 플랫폼 팀이 설치하면 자체 NVIDIA GPU 인프라 위에서 고객용 관리형 Kubernetes 클러스터를 만들고 운영할 수 있습니다.
핵심 기능
- NVKE API나 nvkectl로 클러스터를 신청하고, 머신은 NICo가 공급합니다. 각 워크로드 클러스터마다 독립된 컨트롤 플레인과 etcd가 붙습니다.
- 노드는 합류 전에 TPM을 통한 SPIFFE/SPIRE 증명을 마쳐야 하며, 통과한 뒤에야 합류 자격 증명을 받습니다.
- 노드 풀의 생성, 확장·축소, 삭제를 지원하고, Kubernetes 버전 업그레이드와 노드 교체까지 다룹니다.
- 로컬 퀵스타트에서는 모의 머신 위에 개발용 관리 플레인과 워크로드 클러스터 하나를 띄울 수 있어 NVIDIA 계정이 필요 없습니다.
대상 사용자: 자체 GPU 자원을 갖춘 플랫폼 팀에 적합합니다. 로컬 평가에는 Linux 호스트나 VM, 6 CPU, 12GiB 메모리, 100GiB 디스크, Docker와 가상 TPM이 필요하고, 정식 설치에는 NICo 연동이 필요합니다.
What it is: NVKE is NVIDIA's management plane that platform teams install to run a managed Kubernetes service on their own GPU infrastructure.
Key capabilities
- Clusters are requested through the NVKE API or nvkectl; NVKE provisions machines via NICo, and each workload cluster gets its own control plane and etcd.
- Nodes attest through SPIFFE/SPIRE using their TPM before they receive join credentials.
- Node pools can be created, scaled and deleted; Kubernetes upgrades and node replacement are handled from the same plane.
- A local quickstart runs a development management plane and a workload cluster on simulated machines, with no NVIDIA account required.
Who it is for: Platform teams operating their own GPU hardware.
README · 详细文档
来源 · 查看原文
NVIDIA Kubernetes Engine (NVKE)
Run a managed Kubernetes service on your own NVIDIA GPU infrastructure. NVIDIA Kubernetes® Engine (NVKE) provides the management plane that platform teams install to create and operate Kubernetes clusters for their customers. Each workload cluster has its own Kubernetes control plane, etcd and node pools. You operate the NVKE management plane; your customers use their clusters through the Kubernetes API and kubectl.
Preview: NVKE is available as a preview. APIs, configuration and behavior can change between releases, and we do not recommend NVKE for production workloads. See Preview status and known limitations.
Get started · Documentation · Contribute · Get help
Getting started
| Your goal | Start here | What you get |
|---|---|---|
| Evaluate without GPU hardware | Local quickstart | A development management plane and a workload cluster on simulated machines. No NVIDIA account is required. |
| Install on your infrastructure | Plan your installation | The prerequisites and sequence for preparing nodes, bootstrapping a management cluster and installing its services. |
| Build or contribute | Build from source | The NVKE binaries and the contributor development loop. |
The local quickstart runs on a Linux host or VM, amd64 or arm64, with at least 6 CPUs, 12 GiB of free memory and 100 GiB of free disk. It requires Docker, virtual TPM support and the tools listed in the guide. Follow its setup through workload-cluster creation and confirm the cluster's nodes report Ready. On macOS, use the local site guide, which runs the evaluation inside a Colima virtual machine.
For a real installation, you supply the machines, networking, node images and registries, and configure access to NVIDIA Infra Controller (NICo). NICo is the sole compatible infrastructure provider at preview. The platform and version reference lists validated combinations and pinned dependencies.
What NVKE does
- Creates independent workload clusters. Request clusters through the NVKE
API or nvkectl; NVKE provisions machines through NICo and forms Kubernetes clusters with their own control planes.
- Manages workload cluster lifecycle. Create, scale and delete node pools,
upgrade Kubernetes and replace nodes. See the node pool guide for the manual steps and preview limits on replacement and upgrades.
- Establishes node identity. Nodes attest through SPIFFE/SPIRE using their
TPM before receiving join credentials. Encryption of etcd data is available per cluster.
- Connects builds to deployment. Its companion project,
NVIDIA Kubernetes Recipes (NVKR), builds node images and NVKE components from pinned inputs. NVKE deploys those artifacts; NVKR owns their build and release evidence.
The preview needs explicit operator configuration: API authentication is off and the API uses plain HTTP after installation. Configure API authentication and protected access before admitting callers. The management cluster does not upgrade, scale or replace itself, and there is no management-plane upgrade or backup/restore procedure. FDE node images are for evaluation and provide no data-at-rest confidentiality. Read the known limitations before choosing an evaluation or installation path.
Overview
The diagram shows the NVKE product family, how it sits on NICo and your GPU machines, and which components talk to each other.
NVKE product family. NVKR builds and signs artifacts and publishes them to a registry. The operator installs the management cluster's components, the NVKE management plane, CAPNICo and NVKE observability, from the charts and images in the registry. The management plane requests machines through CAPNICo, which calls NICo, and drives each workload cluster. NICo provisions NVIDIA GPU machines from the node OS image, and those machines become the workload cluster's Kubernetes nodes, each running nvke-agent, under the cluster's Kubernetes control plane. The accelerated runtime produced by AICR and NVKE observability are optional in the workload cluster. The customer uses kubectl against the control plane.
NVKE is not a Kubernetes distribution and not a Cluster API flavour. It is a self-hosting factory for Kubernetes clusters: a throwaway seed cluster stands up a management cluster, and the management plane on it then provisions and lifecycle-manages many isolated workload clusters on demand.
An installation has two kinds of Kubernetes cluster:
- The management cluster runs the NVKE management plane and infrastructure
controllers. nvkectl forms it using a temporary seed cluster; installing the management-plane services is a separate step.
- Workload clusters run customer applications. The management plane creates
and operates them through NICo, Cluster API and the node agent.
Read What is NVKE for the operator workflow and Architecture for the implementation and data flows.
Build from source
Use Go 1.27.3, the version pinned in go.work, and GNU Make 4 or later. Public Go modules must be reachable on the first build. Flox is optional and supplies the repository's development tools; on macOS, it also supplies GNU Make 4. See Development for toolchain setup.
git clone https://github.com/dsx-ai-factory/nvke.git
cd nvke
make build
This builds the workspace and writes nine binaries to bin/: agent, updater, controller, nvkectl, capd-reboot-controller, nvke-os-image-check, management-engine, tenant-api and operator-api. Building does not start a management plane or create a cluster. The node agent runs on Linux.
The workspace guide explains the modules and outputs. For local services and test environments, see Local development setup. Before submitting a change, follow CONTRIBUTING.md and run make preflight; it selects checks for the modules you changed.
Documentation
| Task | Guide |
|---|---|
| Prepare nodes and bootstrap the management cluster | Bootstrap the management cluster |
| Install NVKE services | Install the management plane from the deploy path |
| Build node images and supply release artifacts | Get NVKE artifacts from NVKR |
| Create and manage customer clusters | Create a workload cluster, Manage node pools |
| Give a customer access | Access a workload cluster |
| Inspect cluster health and telemetry | Observe NVKE and its clusters |
The documentation index links the remaining guides and references.
Contributing and support
Contributions, bug reports and documentation improvements are welcome. Start with CONTRIBUTING.md; open an issue before substantial work so maintainers can agree on the approach.
- Questions: GitHub Discussions.
- Chat: the
#nvkechannel in the DSX AI Factory Slack.
- Bugs and feature requests: GitHub Issues.
- Security vulnerabilities: follow SECURITY.md and report privately.
- Community: Code of Conduct, Governance,
Maintainers and Support.
- Releases: release process.
- CI health: the CI dashboard
shows the last thirty runs of every workflow and refreshes hourly.
Trademarks
Kubernetes® is a registered trademark of The Linux Foundation in the United States and other countries. NVIDIA and the NVIDIA logo are trademarks and/or registered trademarks of NVIDIA Corporation in the U.S. and other countries. Other company and product names may be trademarks of the respective companies with which they are associated.
License
Apache License 2.0. See LICENSE and NOTICE.
Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.