gitlawrandjialin
6b47bacfac
GPU Service today only schedules on Kubernetes clusters; Docker / cloud clusters can't host the CRDs. Without any awareness of that, Org members whose Org has no K8s cluster (and no cluster_access grant on one) saw a menu they couldn't use and a form that bottomed out with backend errors. Two changes lock the UX down: - Boot probes the caller's cluster list once and stashes hasKubernetesCluster in initialState. A new canSeeGpuService predicate gates the menu — admins and Org owners always see it (they can add the cluster); everyone else only sees it when a reachable K8s cluster actually exists. - The instances page filters its own cluster list to Kubernetes before deciding what to show. With nothing reachable we render the Deployments-style 'No clusters available. Add a Kubernetes cluster to get started.' empty state and hide the create-instance CTA; admins and Org owners additionally get the 'Add cluster' button that jumps to cluster management.
GPUStack UI
UI for GPUStack.
Installation
- Nodejs 16.0+(with NPM)
If you're on Mac
brew install node
npm install -g pnpm
- Setup
git clone https://github.com/gpustack/gpustack-ui/
- Install dependencies
cd gpustack-ui
pnpm install
Usage
- Run development server (at http://localhost:9000)
npm run dev
- build release
npm run build
Bugs & Issues
- Please submit bugs and issues with a label
ui
Links
- Official website: https://gpustack.ai/
- Documents: https://docs.gpustack.ai/latest/overview/