Add platform-specific installation guides: GKE, AKS, Huawei Cloud CCE, Tencent TKE, IBM Cloud, OpenShift, etc.

Aperta
  • Qualcosa non va?
#795 22 commenti 0 reazioni 3 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@moezdil ci sta già lavorando.

Dal 3/11/2026.

  • #804 di @Junie06 — chiusa senza merge

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

area/docs good first issue kind/documentation kind/feature

Description

The Installation section currently contains only one platform-specific guide — HAMi on AWS — and that page mainly covers the AWS Marketplace install. There are no equivalent production deployment guides for the other major managed-Kubernetes and self-managed platforms where HAMi users commonly run GPU workloads.

Current state

docs/installation/ today:

  • online-installation.md, offline-installation.md, prerequisites.md, upgrade.md, uninstall.md, webui-installation.md — generic, platform-agnostic
  • aws-installation.md — the only platform guide (Marketplace-focused)
  • how-to-use-hami-dra.md, how-to-use-volcano-vgpu.md, how-to-use-volcano-ascend.md, configure-cdi.md — feature-specific

The generic Helm docs do not cover platform differences that matter in production: GPU driver provisioning on GPU node pools, conflicts with the platform's own NVIDIA device plugin (double registration), node taints/tolerations, image registry access/mirrors, and platform security constraints (e.g. OpenShift SecurityContextConstraints).

Proposed guides

  • Google Cloud (GKE)
  • Microsoft Azure (AKS)
  • Huawei Cloud (CCE)
  • Tencent Cloud (TKE)
  • IBM Cloud (IKS / Red Hat OpenShift on IBM Cloud)
  • Red Hat OpenShift (self-managed)
  • Other candidates by demand: Alibaba Cloud (ACK), Volcano-based platform distributions, etc.

What each guide should cover

Following the structure of aws-installation.md, but production-oriented:

  1. Prerequisites — GPU node pool creation, NVIDIA driver management options on that platform, required CLI tools and permissions.
  2. Platform-specific install — Helm values differences, nodeSelector/tolerations for GPU nodes, and how to disable/avoid the platform's default GPU device plugin so HAMi's device plugin is the only one registering GPUs.
  3. Production considerations — scheduler HA, image pull via platform registries/mirrors, offline/air-gapped install where applicable.
  4. Verification — expected pod states plus a smoke-test workload that requests a shared vGPU.
  5. Platform gotchas & troubleshooting pointers — e.g. driver pre-installed by the cloud vendor, MIG support caveats on managed control planes, SCC requirements on OpenShift.

Each new page also needs a sidebars.js entry and a Chinese mirror under i18n/zh/docusaurus-plugin-content-docs/current/.

Use Case

Users deploying HAMi on GKE / AKS / CCE / TKE / OpenShift currently have no official guidance and hit predictable, platform-specific problems (device plugin conflicts, driver provisioning, SCCs). Official per-platform guides would reduce repeated community questions and make HAMi a credible option for production deployment beyond AWS.

Related

  • #689 — RFC: Reorganize the HAMi docs
  • #656 — [LFX Mentorship] Expand HAMi GPU-sharing tutorials, labs, and troubleshooting guides
Lingua principale
JavaScript
Stelle
11
Fork
111
Merge medio
2g 2h
PR unite (30g)
62

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Project-HAMi/website

Tutte le issue di Project-HAMi/website

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.