Configuration Input

To maximize flexibility, configuration input from multiple sources is combined prior to activation. The complete configuration is stored in the cluster as ConfigMaps and Secrets in a namespace reserved for configuration data. Once the data is stored in the cluster, any subsequent interaction can use the stored data without re-entering the data.

The following input sources are considered when preparing a configuration for activation or installation:

• Command line flags

  All configuration fields can be set directly via command line flags. Refer to the command line flags for the full list.

• Onboarding file

  The file downloaded from the IE Hub contains basic information about the instance (such as ID, name, ...). It also contains an activation token. Note that this token has an expiration date after downloading the onboarding file. Alternatively, you can use the exported onboarding file.

• Custom configuration file

  An additional file can be used to add parameters which are not part of the IE Hub onboarding file. This file is in the JSON format and defined below. To use such a configuration file, add the file via the --values command line flag.

• Cluster stored configuration

  After the initial activation, the configuration is also available in the cluster and can be read back.

• Generated secrets

  Before the first activation, some secrets (keys, passwords) must be generated. If these secrets are not available in any of the configuration inputs, they will be generated automatically. The activation process then connects the new keys to the instance in the backend.

Entries higher in the list take precedence over parameters defined by entries lower in the list. This means that command line flags always override any saved configuration.

After all parameters are read, the combined configuration is stored in the cluster (newly created or updated).

To print the final configuration on stdout after all inputs have been applied, set the -v --log-config flag.