Configuring MATRIXX Using Helm
Configure MATRIXX by adding values for properties from the MATRIXX Helm chart in your Helm values file. The MATRIXX Helm chart includes component sub-charts in a hierarchy of reusable components.
In your Helm values file, you only set the values you need. These values are merged with the default values in the MATRIXX Helm chart. Set an object to a blank or empty object to effectively remove 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). If you set an entire branch to a blank or
empty object, for example empty braces {}, you might unset multiple
values. This is also what happens when you use Helm chart properties to pass in
Kubernetes-defined object structures such as resources or affinity rules. The structure
you give replaces the default structure. No merge takes place.
For more information about Kubernetes structures that can be overridden with structures passed in using a Helm values file (or files), see the discussion about other overrides.
--set
option) from the helm install, helm upgrade, and
helm template commands.MATRIXX Engine Management Methods
There are three available MATRIXX Engine management methods in cloud native MATRIXX deployments:
- Engine Controller
- Engine Operator
- Topology Operator
The engine configuration documented in the following sections is oriented towards the
Engine Controller and Engine Operator methods. For example, these sections include
use of the
global.topology.domains[x].subdomains[y].engines[z].external
property when configuring engines across multiple namespaces and clusters.
For Topology Operator usage and configuration information, see the discussion about Topology Operator.