# Coreweave Enterprise Rbac

> Configure RBAC and namespace isolation for CoreWeave multi-team GPU access. Use when managing team permissions, isolating GPU quotas, or implementing namespace-level access control. Trigger with phrases like "coreweave rbac", "coreweave permissions", "coreweave namespace isolation", "coreweave team access".

- Skill: `jeremylongshore/coreweave-enterprise-rbac` (Agent Skill)
- Install (CLI): `npx skillmds@latest add jeremylongshore/coreweave-enterprise-rbac`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jeremylongshore/coreweave-enterprise-rbac/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: jeremylongshore (https://skillmd.com/u/jeremylongshore)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/jeremylongshore/coreweave-enterprise-rbac

---


# CoreWeave Enterprise RBAC

## Namespace-Per-Team Pattern

```yaml
# Team namespace with GPU quota
apiVersion: v1
kind: ResourceQuota
metadata:
  name: ml-team-gpu-quota
  namespace: ml-team
spec:
  hard:
    requests.nvidia.com/gpu: "8"
    limits.nvidia.com/gpu: "8"
    persistentvolumeclaims: "10"
    requests.storage: 2Ti
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: ml-team-access
  namespace: ml-team
subjects:
  - kind: Group
    name: ml-engineers
    apiGroup: rbac.authorization.k8s.io
roleRef:
  kind: ClusterRole
  name: edit
  apiGroup: rbac.authorization.k8s.io
```

## Read-Only Access for Monitoring

```yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: ml-team-readonly
  namespace: ml-team
subjects:
  - kind: Group
    name: ml-managers
roleRef:
  kind: ClusterRole
  name: view
  apiGroup: rbac.authorization.k8s.io
```

## Resources

- [CoreWeave CKS](https://docs.coreweave.com/docs/products/cks)
- [Kubernetes RBAC](https://kubernetes.io/docs/reference/access-authn-authz/rbac/)

## Next Steps

For migration strategies, see `coreweave-migration-deep-dive`.