Configuring your Edge site with the values.yaml file

The values.yaml file is included with the Edge site Helm chart and contains the complete configuration for your Edge site. You can update this file if your organization has specific infrastructure requirements that go beyond the default Edge site installation. While the values.yaml file is primarily used during Helm installation, you can set any Helm value post-installation using the edgecli update command with the --set flag.

Note For the most up to date descriptions of all available fields, review the values.yaml file included with your Edge site installation.

Update configuration parameters

Prerequisites

You have downloaded an Edge site installer.

Run the following command, replacing <helm-yaml-path-to-key> with the path to the field you want to update and <value> with the new value:

Copy 
edgecli update --set <helm-yaml-path-to-key>=<value>

To see available flags, run the following command:

Copy 
edgecli update --help

The command returns the following output:

Update configuration parameters

Usage:
edgecli update [flags]

Flags:
  --set stringArray   Set values on the command line (can specify multiple or separate values with commas: name1=val1,name2=val2)

Global Flags:
  -h, --help
  -l, --loglevel string      Cli Log Level: INFO, DEBUG, WARN, ERROR (default "INFO")
  -n, --namespace string     The namespace edge is installed in (default "collibra-edge")
  -s, --structured-logging   Cli to Log in JSON format

The following table describes the available flags:

Flag Description
--set Sets one or more configuration values. You can specify multiple values using commas. For example, name1=val1,name2=val2.
-h, --help Shows the available flags and their descriptions for the update command.
-l, --loglevel Sets the CLI log level. Accepted values are INFO, DEBUG, WARN, and ERROR. The default is INFO.
-n, --namespace The namespace where Edge is installed. The default is collibra-edge.
-s, --structured-logging Enables JSON format for CLI log output.

Example: Configuring affinity and node selection

You can use the values.yaml file to control which Kubernetes nodes Edge site components are scheduled on. The values.yaml file supports three affinity and node selection blocks:

  • A global block that applies to all pods by default.
  • A per core pod block that overrides the global block for that pod.
  • A global block for jobs.
Note Replace core-pod-name, node-label-key, and node-label-value with the values from your values.yaml file and your Kubernetes node labels. The per-pod block takes precedence over the global block.

For example, you want to isolate heavy job workloads to a dedicated node pool:

Copy 
global:
  scheduling:
    # Static pods: pin to general-purpose nodes
    nodeSelector:
      node-pool: edge-core
     
    # Job pods: route to the high-memory pool
    jobNodeSelector:
      node-pool: edge-jobs
    jobTolerations:
      - key: "workload"
        operator: "Equal"
        value: "edge-jobs"
        effect: "NoSchedule"

What's next