Optimizer Hub Generic Defaults

Flag to define if the Management Gateway is enabled to expose the REST APIs for ReadyNow Orchestrator and/or Cross-Region Sync.

The port used by the Management Gateway.

For Deployment/StatefulSet

For Deployment/StatefulSet

For POD

For POD

For Service

Limit of rolling profile history entries

Enabling of caching the content on the gateway

The fixed size of content cached on the gateway

Time required after the last profile update, after which the profile is considered completed and updates are no longer possible, duration specified in format PnDTnHnMn.nS.

Flag to define if profiles must be recorded after the maxGeneration has been reached. You can use this flag for debugging purposes.

The number of concurrent copies of a specific generation ReadyNow Orchestrator accepts before it tells other JVMs trying to write the same generation of the same profile name to stop

Maximum number of generations ReadyNow Orchestrator accepts for a profile name. Note that here is no 'unlimited' value available

Limit on the input profile size, in bytes.

Enabling of automatic repository clean-up

Determines the threshold for the blob data usage, at which ReadyNow Orchestrator initiates its cleanup process.

Time limit after which the profile name gets removed if it was not requested within the given duration specified in format PnDTnHnMn.nS.

By default, no limit is defined. You need to specify a value if you want to enable complete cleanup of unused profiles.

Minimal size (bytes) threshold for all generations unless per-generation flags are specified. Per-generation flags take precedence over the global setting, but the global might be used as a generation 0 setting in case it is not specified in the corresponding per-generation setting.

Minimal size thresholds for each generation. In case a generation is missing in the list, it inherits a value from the previously specified generation or the global setting, if there is no previous generation specified.

List of pair <generation>:<size>, separated by \,.

For more information, check Understanding ReadyNow Orchestrator Generations.

See previous.

Duration specified in format PnDTnHnMn.nS.

See minProfileSizePerGeneration.

List of pair <generation>:<duration>, separated by \,. The duration must be specified in the format PnDTnHnMn.nS.

For more information, check Understanding ReadyNow Orchestrator Generations.

Defines the maximum number of profile generations to be synced from peers. Profiles with a higher generation are not synced from peers.

Define if Cross-Region Sync needs to be enabled. You must also enable the Management Gateway for this setting to become effective.

A comma separated list of peer Management Gateway URLs from other Optimizer Hub instances to include in the syncing process.

Initial delay for the periodic synchronization task.

Defines periodicity of a synchronization with the specified Optimizer Hub peers.

Flag to specify if the automatic Code Cache cleaner must be enabled.

Target size for the Code Cache cleaner.

Interval at which the Code Cache cleaner checks whether the current usage is bigger than targetSize. If so, the cleanup process is triggered. This process deletes the Code Cache items that are least recently used to get below the targetSize.

Name of the existing Secret object to use. A new secret is created if the name is empty.

Name of the key for the accessKey value in Kubernetes secret. It can be renamed to the match names in an existing secret.

The default value for accesskey, used when a new secret is created.

The name of the key for the secretkey value in Kubernetes secret. It can be renamed to match names in an existing secret.

The default value for s3.secretkey, used when a new secret is created.

The name of an existing secret object to use. A new secret is created if the name is empty.

The name of the key for the connectionStringSecretKey value in Kubernetes secret. It can be renamed to match names in an existing secret.

The name of the key for sasTokenSecretKey in K8S Secret. It can be renamed to match names in existing Secret

The total number of vCores that gets allocated to the Optimizer Hub service. The default value is the amount of vCores necessary to start one instance of Optimizer Hub, so that the service is operational.

minVCores and maxVCores have the same formula as vCores, but are applied when autoscaling is enabled. The value is used by the Optimizer Hub service to adjust the sizing of the instance to try to meet your timeToClearOptimizationBacklog limit for all the JVMs that request compilations.

The default max value is dimensioned to be able to allocate 10 compile brokers.

Flag to specify if SSL must be enabled for Optimizer Hub connections from JVMs.

Specify the certificate and private keys directly as values. This is the simplest way to run quick experiments in a controlled environment, especially when you’re installing from the Helm repository.

Example:

 
ssl:
  value:
    cert: |-
      -----BEGIN CERTIFICATE-----
      ...
      -----END CERTIFICATE-----
    key: |-
      -----BEGIN PRIVATE KEY-----
      ...
      -----END PRIVATE KEY-----

Specify the certificate and private key file paths.

When you use a separate chain to manage your certificate, you can point the deployment to a custom secret in the installation namespace. Such a secret needs to have keys named cert.pem and key.pem.

This is the most secure way to add certificates. is .