Overview

Managing zxporter Resource Allocation and Cleanup

Update zxporter

curl https://raw.githubusercontent.com/devzero-inc/zxporter/refs/heads/main/dist/installer_updater.yaml | kubectl apply -f -

Increase Resource Requests for zxporter

By default, zxporter requests the following resources:

• Memory: 128Mi
• CPU: 200m

If you're running zxporter on a large Kubernetes cluster, you may need to allocate more resources. Use the following command to increase memory and CPU requests:

kubectl patch deployment devzero-zxporter-controller-manager -n devzero-zxporter --patch '{
  "spec": {
    "template": {
      "spec": {
        "containers": [
          {
            "name": "manager",
            "resources": {
              "requests": {
                "memory": "512Mi",
                "cpu": "500m"
              }
            }
          }
        ]
      }
    }
  }
}'

Delete zxporter from your cluster

kubectl delete all --all -n devzero-zxporter

Resources created by the installer

When you install the zxporter operator, the following Kubernetes resources are created in the devzero-zxporter namespace:

Namespaces and Service Accounts

• Namespace: devzero-zxporter
• ServiceAccounts:
  • devzero-zxporter-controller-manager
  • prometheus-server
  • prometheus-kube-state-metrics
  • prometheus-prometheus-node-exporter
  • prometheus-prometheus-pushgateway
  • node-exporter-prometheus-node-exporter

RBAC (Roles and Bindings)

• Role: devzero-zxporter-leader-election-role
• RoleBinding: devzero-zxporter-leader-election-rolebinding
• ClusterRoles:
  • devzero-zxporter-manager-roleresources
  • devzero-zxporter-collectionpolicy-editor-role
  • devzero-zxporter-collectionpolicy-viewer-role
  • devzero-zxporter-metrics-auth-role
  • devzero-zxporter-metrics-reader
  • prometheus-server
  • prometheus-kube-state-metrics
• ClusterRoleBindings:
  • devzero-zxporter-manager-rolebinding
  • devzero-zxporter-metrics-auth-rolebinding
  • prometheus-server
  • prometheus-kube-state-metrics

Config and Secrets

• ConfigMap: devzero-zxporter-env-config
• ConfigMap: prometheus-server
• ConfigMap: devzero-zxporter-config (inferred from deployment conventions)
• Secret: kube-root-ca.crt (automatically created)

Deployments

• devzero-zxporter-controller-manager
• prometheus-kube-state-metrics
• prometheus-prometheus-pushgateway
• prometheus-server

DaemonSets

• prometheus-prometheus-node-exporter
• node-exporter-prometheus-node-exporter

Services

• devzero-zxporter-controller-manager-metrics-service
• prometheus-kube-state-metrics
• prometheus-prometheus-node-exporter
• prometheus-prometheus-pushgateway
• prometheus-server
• node-exporter-prometheus-node-exporter

Metrics & Monitoring

• Exposes metrics via:
  • Prometheus Node Exporter
  • Kube-State-Metrics
  • PushGateway
• Resource usage is tracked for operator and Prometheus components.

Note: The operator reads only metadata and scheduler configuration required for workload analysis — no secrets or sensitive pod-level data is accessed.

Alternative image registries

By default, DevZero uses Dockerhub to host images. As an alternative, to use our ECR instead: change devzeroinc, to public.ecr.aws/devzeroinc (docker pull devzeroinc/zxporter becomes docker pull public.ecr.aws/devzeroinc/zxporter). All image repository names and tags are maintained consistently in both Dockerhub and ECR.

When using our helm charts, use --set image.repository=public.ecr.aws/devzeroinc.