Configuring Resource Limits

This page describes how to configure resource limits for various components of the TrilioVault for Kubernetes application.

Variables

Variables have been created to be able to configure resource limits for Trilio pods.

  • metadataJobLimits - Specifies limits for all meta-data related and target mounting jobs like target-validator, meta-snapshot, pre-restore-validation, meta-restore etc

  • dataJobLimits : Specifies limits for Datamover jobs

  • deploymentLimits : Specifies limits for helm chart deployments. Not applicable for OCP

Configuring limits in Upstream Kubernetes

Directly specify the resource limits in the TVM CR spec:

apiVersion: triliovault.trilio.io/v1
kind: TrilioVaultManager
metadata:
labels:
triliovault: k8s
spec:
trilioVaultAppVersion: latest
helmVersion:
version: v3
applicationScope: Namespaced
restoreNamespaces: ["kube-system", "default"]
metadataJobLimits:
cpu: 500m
memory: 512Mi
dataJobLimits:
cpu: 1200m
memory: 1536Mi
deploymentLimits:
cpu: 250m
memory: 512Mi

Configuring limits in OCP

During installation on OCP, a confimap k8s-triliovault-configcontaining the default limits is created. Edit the configMap to change default limits as per requirement.

Kubectl edit configmap k8s-triliovault-config -n <NAMESPACE>

ConfigMap example:

apiVersion: v1
kind: ConfigMap
metadata:
labels:
app.kubernetes.io/instance: k8s-triliovault-config
app.kubernetes.io/managed-by: k8s-triliovault
app.kubernetes.io/name: k8s-triliovault
app.kubernetes.io/part-of: k8s-triliovault
name: k8s-triliovault-config
data:
dataJobLimits: '{"cpu":"1","memory":"1536Mi"}'
metadataJobLimits: '{"cpu":"500m","memory":"512Mi"}