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".From its SKILL.md
npx -y skills add ComeOnOliver/skillshub --skill coreweave-enterprise-rbacAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.7 KB, 343 tokens by cl100k_base, as published. Nobody here has run it
CoreWeave Enterprise RBAC
Namespace-Per-Team Pattern
# 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
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
Next Steps
For migration strategies, see coreweave-migration-deep-dive.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.