Separate platform control from tenant access
Multi-tenant KubeVirt operations need more than Kubernetes permissions alone. Platform teams need global controls, while application teams need scoped access to the VMs, services, systems, namespaces, and environments they own.
Dual-layer RBAC
Shepherd combines platform-facing RBAC with application ownership and environment scoping. The goal is to make daily access understandable to users while keeping administrative capabilities under explicit control.
- Platform roles govern global capabilities.
- System and service membership scopes access to managed resources.
- Environment-aware binding helps separate production and non-production responsibility.
Audit trails for shared environments
When many teams share KubeVirt infrastructure, audit history becomes operational data. Shepherd records who requested, approved, and performed changes so reviews do not depend on scattered chat logs or shell history.