Skip to content

Ranger TagSync Pod CPU Configurations

Follow these steps to update the CPU configurations of the Ranger TagSync pod.

  1. SSH into the instance where Privacera Manager is installed.
  2. Navigate to the privacera-manager directory using the following command:
    Bash
    1
    cd ~/privacera/privacera-manager/
  3. Run the following command to copy the sample vars. The -n flag ensures that the file is not overwritten if it already exists.
    Bash
    1
    cp -n config/sample-vars/vars.ranger-tagsync.yml config/custom-vars/
  4. Run the following command to edit the 'var.ranger-tagsync.yml' file.
    Bash
    1
    vi config/custom-vars/vars.ranger-tagsync.yml
  5. Add the following properties in vars.ranger-tagsync.yml to configure the CPU for the Ranger TagSync pod:
Property Name Description Default Value
TAGSYNC_CPU_MIN Minimum amount of Kubernetes CPU to be requested by Ranger Tagsync 0.5
TAGSYNC_CPU_MAX Maximum amount of Kubernetes CPU to be used by Ranger Tagsync 0.5
TAGSYNC_K8S_CPU_REQUESTS Maximum amount of Kubernetes CPU to be used by Ranger Tagsync 0.5
TAGSYNC_K8S_CPU_LIMITS Maximum amount of Kubernetes CPU to be used by Ranger Tagsync 0.5
  • Below is the example of var.ranger-tagsync.yml file with CPU configurations:

YAML
1
2
3
4
 TAGSYNC_CPU_MIN: "0.5"
 TAGSYNC_CPU_MAX: "0.5"
 TAGSYNC_K8S_CPU_REQUESTS: "0.5"
 TAGSYNC_K8S_CPU_LIMITS: "0.5"
6. After updating the properties and restart the service by following these steps:
Bash
1
2
3
cd ~/privacera/privacera-manager
./privacera-manager.sh setup
./pm_with_helm.sh upgrade