Modifying the Resource Limits for Commvault Temporary Pods for Kubernetes

You can specify the maximum and minimum CPU and memory limits for the temporary pods that Commvault spawns during backups and other operations for Kubernetes.

For backups, Commvault deploys one pod per PersistentVolumeClaim, within the namespace of the PersistentVolume that is being protected.

Procedure

From the navigation pane, go to Manage > System.
Click the Additional settings tile.

The Additional settings page appears.
Click Add, and then select Entity settings.

The Add entity settings dialog box appears.
Add the entity settings as follows:

Name	Entity	Category	Type	Value
sK8sWorkerCpuMax	The Kubernetes access node	VirtualServer	String	The maximum CPU that Commvault temporary pods can use. For example, you can enter 250m.
sK8sWorkerCpuMin	The Kubernetes access node	VirtualServer	String	The minimum CPU that Commvault temporary pods can use. For example, you can enter 1m.
sK8sWorkerMemMax	The Kubernetes access node	VirtualServer	String	The maximum memory that Commvault temporary pods can use. For example, you can enter 1Gi.
sK8sWorkerMemMin	The Kubernetes access node	VirtualServer	String	The minimum memory that Commvault temporary pods can use. For example, you can enter 16Mi.