Tenant Configuration Options

NeMo Customizer relies on Kubernetes-level authentication and authorization, with no built-in multi-tenancy. Choose your configuration based on your needs:

Configuration	Description	Considerations
Single-tenant (Recommended)	One tenant per cluster/namespace	- Simplest to manage - Complete isolation through Kubernetes
Multi-tenant	Multiple tenants sharing a cluster	- Limited isolation between users - Shared visibility of customizations - Requires careful PVC and dataset access control

Warning

In multi-tenant setups, users can see all customizations in the cluster and may have access to shared PVC resources.