Configuring MATRIXX Gateways and Web Apps
In a non-containerized installation of MATRIXX, configure MATRIXX gateways and web apps using files in the /opt/mtx/conf directory in the pod(s) hosting those components. In a cloud native deployment, configuration files can be provided in the /opt/mtx/conf directory of the component container(s) using the following methods:
Configuration by Configuration Source
Configuration sources are defined at a global level and can be used by as many components as needed. Configuration for MATRIXX gateways and web apps can come from configuration sources based on Docker images, Git repositories, or Kubernetes ConfigMaps. Attributes of a configuration source can be overridden when referenced at the component level.
For more information about sources that can provide configuration information, see the discussion about configuration sources in MATRIXX Configuration.
Configuration by Kubernetes ConfigMap
Component configuration files can be expressed as a Kubernetes ConfigMap for synchronization with the /opt/mtx/conf directory, overwriting any existing files, as specified with the sub-chart_name.configuration.container.configmap configuration property. All keys underneath this option represent the files to create. The following shows how to define an rsgateway.yaml file and an rsgateway_users.yaml file to be written to the /opt/mtx/conf directory:
rsgateway:
configuration:
container:
configmap:
rsgateway.yaml: |-
my:
property:
one: abc
two: def
rsgateway_users.yaml: |-
user: "{bcrypt}5f4dcc3b5aa765d61d8327deb882cf99, MTX_ROLE_RSG_CREATE, MTX_ROLE_RSG_READ, MTX_ROLE_RSG_UPDATE, MTX_ROLE_RSG_DELETE, MTX_ROLE_RSG_STD"
For more information, about using ConfigMaps, see the discussion about dynamic configuration in MATRIXX Configuration. For information about supported encoding algorithms (such as bcrypt), see the discussion about password encoding in MATRIXX Security.