Define wether the database node is installed.
Is set to false in ReadyNow Orchestrator only mode, using values-disable-compiler.yaml
Optimizer Hub is shipped as a Helm chart with all the defaults as specified in the values.yaml file. Here you find a list of the most important generic values that can be modified to match Optimizer Hub to your environment.
Specific settings can be found on the configuration pages of the service itself, for example, "Configuring ReadyNow Orchestrator > ReadyNow Orchestrator Defaults".
Option | Description | Default |
---|---|---|
db.enabled |
Define wether the database node is installed. Is set to false in ReadyNow Orchestrator only mode, using |
true |
Option | Description | Default |
---|---|---|
dbschema.auto-recreate.enabled |
If enabled, automatically recovers from database pod restarts with loss of schema. If you have a database and this database is not using a persistence volume, this setting must be set to true, otherwise you need a manual interaction if the pod is restored. |
false |
Option | Description | Default |
---|---|---|
mgmtGateway.enabled |
Define if the Management Gateway needs to be enabled to expose the REST APIs for ReadyNow Orchestrator and/or Cross-Region Sync. |
false |
mgmtGateway.service.httpEndpoint.port |
The port used by the Management Gateway. |
8080 |
Option | Description | Default |
---|---|---|
synchronization.enabled |
Define if Cross-Region Sync needs to be enabled. You must also enable the Management Gateway for this setting to become effective. |
true |
synchronization.peers |
A comma separated list of peer Management Gateway URLs from other Optimizer Hub instances to include in the syncing process. |
|
synchronization.initialDelay |
Initial delay for the periodic synchronization task. |
PT180s |
synchronization.period |
Defines a periodicity of a synchronization with the specified Optimizer Hub peers. |
PT30s |
See "Sizing and Scaling your Optimizer Hub Installation > Configuring Capacity".