Configuring MATRIXX Digital Commerce Using Helm

Configure MATRIXX Digital Commerce by adding values for properties from the MATRIXX Helm chart to the values.yaml file. The MATRIXX Helm chart includes component sub-charts in a hierarchy of reusable components.

In the values.yaml file, you only set the values you need. These values are merged with the default values in the MATRIXX Helm chart. If you provide a null, blank or empty object for a property, that effectively un-sets the default value for that property.

The properties and their values describe an object tree with objects (branches) containing values (leaves) or other objects (branches). By setting an entire branch to a null or empty object, for example empty braces {}, you potentially unset multiple values. This is also what happens when you use Helm chart properties to pass in a Kubernetes-defined object structure, such as resources or affinity rules. The structure you provide replaces the default structure. No merge takes place.

For more information about the Kubernetes structures that can be overridden with structures passed in using the values.yaml file, see the discussion about other overrides.

Note: Each sub-chart is accompanied by a values.schema.json file. Helm uses this file to validate the object created from values in the values.yaml file (and anything passed to Helm in command line arguments using the --set option) from the helm install, helm upgrade, and helm template commands.