Resource Requirements and Limits

This page provides resource requirements for Trilio for Kubernetes pods

Deprecated Documentation

This document is deprecated and no longer supported. For accurate, up-to-date information, please refer to the documentation for the latest version of Trilio.

Resource Requirements and Limits

The table below provides resource related information for Trilio for Kubernetes pods.

The overall resource requirements of Trilio for Kubernetes are dependent on the number of data protection and data management activities that are being performed. For example, a T4K instance with 100 backupPlans may need more resources if all backupPlans are configured to trigger the backup at the same time, compared to a T4K instance with 100 BackupPlans configured to be triggered at staggered intervals.

The information contained herein can be leveraged to assign Resource Quotas and Limit Ranges for namespaces and resources within namespaces.

Pod Name	CPU request (milliCore/ milliCPU)	CPU limit (milliCore/ milliCPU)	Memory request	Memory Limit
Target Validator Backup Cron Snapshot Metadata Upload (backupPlan, backup) Retention Restore Validation Restore Metadata Backup Cleaner Resource Cleaner	0.01	0.1	10 Mi	256 Mi
Datamover Upload Datamover Restore	0.1	1	800 Mi	2 Gi
Webhook Control-plane Exporter	0.01	-	10 Mi	128 Mi

To scale T4K as an application, the control plane components (deployments) can be scaled as per Kubernetes documentation. Services associated to the components, automatically will load balance the traffic.