Apply MATRIXX Engine Configuration Changes

Configuration of MATRIXX Engine is applied using a configuration source.

Procedure

  1. Update kubernetes/example-engine-config-sideloader/config/resource_create_config.info with your configuration changes.
  2. If any necessary configuration questions are missing from kubernetes/example-engine-config-sideloader/config/resource_create_config.info, add them from the superset in create_config.info.
    For more information, see the discussion about configuration input settings in MATRIXX Configuration.
  3. Change directory to the kubernetes directory.
  4. Build your custom configuration image.
    docker build -t sideloader_image_name ./example-engine-config-sideloader
  5. Apply a tag.
    docker tag sideloader_image_name your_image_repository/sideloader_image_name:version-tag
  6. Add the image to your image repository.
    docker push your_image_repository/sideloader_image_name:version-tag

    For more information, see the discussion about obtaining and hosting images.

  7. Update the global.configurationSources.name.docker.image property in your Helm values file with your image name and the new tag, similar to the following example: 
    global:
  configurationSources:
    acme-engine-config:
      docker:
        image: sideloader_image_name:tag
        registry: acme-insecure-docker-register
  8. If the configuration changes affect Network Enablers in the topology, delete the Network Enabler pod(s).
    kubectl delete pod network_enabler_pod_name
  9. Apply the changes in your Helm values file (and, by extension, the configuration source) with the helm upgrade command:
    helm upgrade installation_name chart -f helm_values_file.yaml