NewCompare CPU & GPU pricing across AWS, Azure & GCP

RBAC & Permissions

Kubernetes RBAC roles and permissions used by each DevZero operator.

RBAC & Permissions

Each DevZero operator uses a dedicated ServiceAccount with a minimal ClusterRole following the principle of least privilege.

Read Operator (zxporter)

Namespace: devzero-system

ClusterRole permissions:

ResourceVerbs
Nodes, Pods, Deployments, StatefulSets, DaemonSets, ReplicaSetsget, list, watch
Services, Endpoints, Ingresses, NetworkPoliciesget, list, watch
PersistentVolumes, PersistentVolumeClaims, StorageClassesget, list, watch
Namespaces, ServiceAccounts, ConfigMaps (metadata only)get, list, watch
HPAs, VPAs, PDBs, PriorityClassesget, list, watch
ResourceQuotas, LimitRangesget, list, watch
Karpenter CRDs (NodePools, NodeClaims)get, list, watch
SecretsNo access

The Read Operator has zero write permissions -- it cannot create, update, patch, or delete any resource.

Write Operator (dakr-op)

Namespace: devzero-system

ClusterRole permissions:

ResourceVerbs
Deployments, StatefulSets, DaemonSetsget, list, watch, patch, update
HPAsget, list, watch, patch, update
Podsget, list, watch
WorkloadRecommendations, NodeGroupRecommendations (CRDs)get, list, watch, create, update, patch, delete
CheckpointRestores (CRDs)get, list, watch, create, update, patch, delete

The Write Operator can only modify Deployments, StatefulSets, DaemonSets, and HPAs -- it cannot access Secrets, ConfigMaps, or other sensitive resources.

Security Operator

Namespace: devzero-system

ClusterRole permissions:

ResourceVerbs
All workload typesget, list, watch
VulnerabilityReports, ConfigAuditReports (CRDs)Full CRUD
ClusterComplianceReports (CRDs)Full CRUD
Jobs (for scan execution)create, delete

The Security Operator reads workload metadata to determine what to scan. It creates Jobs to run Trivy scanners and stores results as CRDs.

Node Operator

Namespace: devzero-system

ClusterRole permissions:

ResourceVerbs
NodesFull lifecycle management
Podsget, list, watch, eviction
NodePools, NodeClaims, provider node classes (EC2NodeClass, AKSNodeClass, GCENodeClass, OCI) (CRDs)Full CRUD
Cloud provider APIsInstance launch, termination
Secrets (kube-system only, AKS)get, list, watch (bootstrap tokens)

On AKS (dzKarp 1.9.1+), the Node Operator's Secret access is scoped to kube-system bootstrap tokens only.

Scheduler (dz-scheduler)

Namespace: devzero-system

ClusterRole permissions:

ClusterRolePermissions
dz-scheduler-kube-schedulerCreate/patch events, manage leases, get/list/watch nodes and pods, create pod bindings, patch pod status, get/list/watch workloads and storage resources
dz-scheduler-volume-schedulerGet/list/patch/update/watch PersistentVolumes, PersistentVolumeClaims, StorageClasses
dz-scheduler-configmap-readerGet/watch/list ConfigMaps

The Scheduler runs with system-cluster-critical priority and tolerates all taints. It has standard kube-scheduler permissions plus read access to ConfigMaps for token resolution.

Cost Operator (trezr)

Namespace: devzero-system

ClusterRole permissions:

ResourceVerbs
ConfigMapsget, list, watch, create, update, patch, delete
Leasesget, list, watch, create, update, patch, delete
Eventscreate, patch

A Role in its namespace also grants get on the one Secret that holds the cluster token, devzero-zxporter-token. The Cost Operator reads no workloads, nodes, or pods. Its cost data comes from your cloud's billing APIs through a cloud identity (IRSA on AWS, Workload Identity on GCP and Azure). See Cost Operator.

Auditing Permissions

Verify what permissions an operator actually has:

# Check Read Operator's ClusterRole
kubectl describe clusterrole devzero-zxporter-manager-roleresources

# Check Write Operator's ClusterRole
kubectl describe clusterrole dakr-operator-role

# Check Scheduler's ClusterRoles
kubectl describe clusterrole dz-scheduler-kube-scheduler
kubectl describe clusterrole dz-scheduler-volume-scheduler

# Check Cost Operator's ClusterRole
kubectl describe clusterrole trezr

# Test specific permissions
kubectl auth can-i get secrets --as=system:serviceaccount:devzero-system:devzero-zxporter-controller-manager
# Expected: no

On this page