nvke README

项目的 README,来自 github.com/dsx-ai-factory/nvke。合并为一个 markdown 文件:README.md。

NVIDIA Kubernetes Engine (NVKE)

License Go

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

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:

Read What is NVKE for the operator workflow and Architecture for the implementation and data flows.

Build from source

Use Go 1.27.4, 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.

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.

nvke (dsx-ai-factory/nvke)

正在搜索数据库…

1.2K ·GitHub
这是什么?NVKE 是 NVIDIA 的管理平面,用于在您自有的 NVIDIA GPU 裸金属服务器上创建和运维 Kubernetes 集群。平台团队负责安装它,之后其客户即可通过 NVKE API、nvkectl 或 kubectl 获得相互隔离的 Kubernetes 集群。
它是 Kubernetes 发行版,还是 Cluster API 的一种变体?都不是。它是一个自托管的工厂:先由一个临时的种子集群搭建管理集群,然后该管理平面按需创建并管理大量相互隔离的工作负载集群。每个工作负载集群都有自己的控制平面、etcd 和节点池。
没有 GPU 硬件,我怎么试用?在支持 Docker 和虚拟 TPM 的 Linux 主机或虚拟机(amd64 或 arm64)上运行本地快速入门,且至少需要 6 个 CPU、12 GiB 可用内存和 100 GiB 可用磁盘。它会在模拟机器上搭建一个开发用的管理平面和一个工作负载集群,无需 NVIDIA 账户。在 macOS 上,指南会在 Colima 虚拟机中运行它。
开始之前需要安装哪些软件?本地快速入门需要 Docker、虚拟 TPM 支持,以及指南中列出的工具。若要从源代码构建,请使用 Go 1.27.3(在 go.work 中固定)和 GNU Make 4 或更高版本,并确保首次构建时可以访问公共 Go 模块。
可以用于生产环境吗?不可以。它目前处于预览阶段,API 和行为可能会在版本之间发生变化。API 身份验证默认关闭,安装后 API 使用明文 HTTP,因此在允许调用方接入之前,请先配置身份验证。管理集群无法自行升级、扩缩容或替换,也没有管理平面的升级或备份/恢复流程。
磁盘上的数据会被加密吗?评估镜像中不会。FDE 节点镜像仅供评估使用,不提供静态数据的机密性保护,因此请勿依赖它们来保护磁盘上的数据。
节点在加入集群之前如何证明自己的身份?每个节点在收到加入凭据之前,会使用其 TPM 通过 SPIFFE/SPIRE 进行远程证明。etcd 数据加密可按集群启用。
日常使用管理平面可以做什么?通过 NVKE API 或 nvkectl 申请集群,然后创建、扩缩容和删除节点池,升级 Kubernetes,并替换节点。底层机器由 NICo 负责供应。替换和升级功能存在预览阶段的限制。
NVKR 是什么?它如何配合工作?NVIDIA Kubernetes Recipes(NVKR)是配套项目,它基于固定的输入构建节点镜像和 NVKE 组件。NVKE 负责部署这些产物,而 NVKR 负责它们的构建和发布证明材料。
有哪些类似的项目?crossplane, talos, nomad, rook, kubernetes, run-ai, containerd, minikube
大小
134.4 MB
星标
1.2K
时长
3个月
提交 · 90 天