This page provides resource requirements for TrilioVault for Kubernetes pods
TrilioVault Pods and CPU/Memory requirements
The table below provides resource related information for TrilioVault for Kubernetes pods.
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)
CPU limit
(milliCore)
Memory request
Memory Limit
Target Validator
Metadata Snapshot
Quiesce
Unquiesce
Metadata Upload
Retention
Restore Validation
Restore Metadata
Backup Cleaner
10
500
10 Mi
512 Mi
Datamover Upload
Datamover Restore
Target Browser
100
1500
800 Mi
5120 Mi
Webhook
Exporter
Dex
Web
Ingress-controller
Resource Cleaner
Backup CronJob
10
200
10 Mi
512 Mi
Web-backend
400
800
1024 Mi
4096 Mi
Control-plane
200
400
512 Mi
2048 Mi
Estimating Memory and CPU requirements for TrilioVault
The overall resource requirements of TrilioVault for Kubernetes will be dependent on the resources of the control plane pods and along with that dependent on the number of data protection and data management activities that are being performed. For example, a Kubernetes cluster with 10 backupPlans may need more resources if all backupPlans are configured to trigger the backup at the same time, compared to a Kubernetes cluster with 15 BackupPlans configured to be triggered at staggered intervals.
Control Plane
At the control plane level, TrilioVault uses the following pods: webhook, control-plane, exporter, web, web-backend, and ingress controller. Based on the table above, the following requirements can be calculated:
1.
CPU requests and CPU limits of 170 milliCore and 1800 milliCore approximately
2.
Memory requests and Memory limits of 170 Mi and 4608 Mi approximately
Data Plane
Depending on the number of backup, restore and target operations happening concurrently and the overall features those operations use, the CPU and memory requirements can be calculated at the data plane level.
1.
Backup operations include -> Metadata snapshot, Quiesce (optional), Unquiesce (optional), Data Upload, Metadata upload, Retention (optional), Backup Cleaner (optional)
2.
Restore operations include -> Restore Validation, Data Restore, Restore Metadata, Unquiesce (optional)
3.
Target Operations include -> Target Validator, Target Browsing (Optional)
Adding up the resources requirements for the different phases for a particular operation will provide the requirements for the entire backup or restore operation.
Maximum Resource Requirements
In order to estimate the maximum memory and CPU that could be utilized by TrilioVault, the biggest pods need to be evaluated running in parallel. For 5 concurrent backups and restores, the maximum amount of CPU and Memory required would be dictated by the Datamover pods running in parallel. Based on the table above, the following can be calculated:
1.
CPU request and CPU limits of 500 milliCore and 7500 millCore approximately
2.
Memory requests and Memory limits of 4000 Mi and 25600 Mi approximately