技能 编程开发 CoreWeave企业级RBAC权限管理

CoreWeave企业级RBAC权限管理

v20260423
coreweave-enterprise-rbac
本技能用于配置CoreWeave平台上的企业级RBAC(基于角色访问控制)和命名空间隔离策略。它指导用户如何为多团队的GPU工作负载设置严格的资源配额和权限边界,有效防止资源争抢(noisy-neighbor),实现资源隔离,并满足企业级的安全和合规性要求。
获取技能
280 次下载
概览

CoreWeave Enterprise RBAC

Overview

CoreWeave runs GPU workloads on Kubernetes, so RBAC maps directly to K8s namespace isolation and ResourceQuotas. Each team gets a dedicated namespace with GPU limits, storage caps, and network policies. This prevents noisy-neighbor problems where one team's training job starves another's inference service. SOC 2 and HIPAA workloads require namespace-level audit logging and team-scoped API key rotation.

Role Hierarchy

RolePermissionsScope
Cluster AdminFull CKS control, namespace creation, quota managementAll namespaces
Team LeadDeploy workloads, manage team API keys, adjust pod limitsOwn namespace
ML EngineerLaunch jobs, access PVCs, view logsOwn namespace
Inference OperatorDeploy/scale inference endpoints, read metricsOwn namespace
ViewerRead-only pod status, logs, GPU utilization metricsOwn namespace

Permission Check

import { KubeConfig, RbacAuthorizationV1Api } from '@kubernetes/client-node';

async function checkNamespaceAccess(user: string, namespace: string, verb: string, resource: string): Promise<boolean> {
  const kc = new KubeConfig();
  kc.loadFromDefault();
  const rbac = kc.makeApiClient(RbacAuthorizationV1Api);
  const review = { apiVersion: 'authorization.k8s.io/v1', kind: 'SubjectAccessReview',
    spec: { user, resourceAttributes: { namespace, verb, resource } } };
  const result = await rbac.createSubjectAccessReview(review);
  return result.body.status?.allowed ?? false;
}

Role Assignment

async function assignTeamNamespace(team: string, group: string, gpuLimit: number): Promise<void> {
  await kubectl(`create namespace ${team}`);
  await kubectl(`create resourcequota ${team}-gpu --namespace=${team} --hard=requests.nvidia.com/gpu=${gpuLimit}`);
  await kubectl(`create rolebinding ${team}-access --namespace=${team} --clusterrole=edit --group=${group}`);
  console.log(`Namespace ${team} created with ${gpuLimit} GPU quota bound to ${group}`);
}

async function revokeAccess(team: string, binding: string): Promise<void> {
  await kubectl(`delete rolebinding ${binding} --namespace=${team}`);
}

Audit Logging

interface CoreWeaveAuditEntry {
  timestamp: string; user: string; namespace: string;
  action: 'gpu_request' | 'deploy' | 'scale' | 'delete' | 'quota_change';
  resource: string; gpuCount?: number; result: 'allowed' | 'denied';
}

function logAccess(entry: CoreWeaveAuditEntry): void {
  console.log(JSON.stringify({ ...entry, cluster: process.env.CW_CLUSTER_ID }));
}

RBAC Checklist

  • [ ] Each team has a dedicated namespace with ResourceQuota
  • [ ] GPU limits set per namespace to prevent resource starvation
  • [ ] RoleBindings use AD/OIDC groups, not individual users
  • [ ] Network policies isolate namespace traffic
  • [ ] API keys scoped to team namespace, rotated quarterly
  • [ ] Viewer role assigned to finance/management for cost visibility
  • [ ] Audit logging enabled for all GPU allocation events

Error Handling

IssueCauseFix
Forbidden: GPU quota exceededNamespace quota reachedIncrease ResourceQuota or free idle pods
RoleBinding not foundGroup name mismatch with IdPVerify AD/OIDC group name matches RoleBinding subject
Namespace not foundTeam namespace not provisionedRun namespace creation script before role assignment
SubjectAccessReview deniedMissing ClusterRole bindingCheck if ClusterRole exists and verb is permitted

Resources

Next Steps

See coreweave-security-basics.

信息
分类 编程开发
名称 coreweave-enterprise-rbac
版本 v20260423
大小 4.3KB
更新时间 2026-04-28
语言