feat: gate GPU Service on Kubernetes cluster availability

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.

This commit is contained in:

gitlawr

2026-05-27 13:41:32 +08:00

committed by

jialin

parent 099b419e34

commit 6b47bacfac

11 changed files with 109 additions and 9 deletions

									
										config/routes.ts
									
		+1
		
												View File
												
				@@ -186,6 +186,7 @@ const baseRoutes = [

				    name: 'gpuService',

				    path: '/gpu-service',

				    key: 'gpuService',

				    access: 'canSeeGpuService',

				    routes: [

				      {

				        path: '/gpu-service',