Initialize the Event Repository Utility
If the global.features.eventLoader configuration property is set to
true, the initialize Event Repository
utility is created as a single-use job that uses a ready processing pod to set up the Event Repository.
The job must also be enabled with the
utilities.initialize-event-repository.enabled property. Initialize Event Repository Properties describes the available configuration
properties.
| Property | Description |
|---|---|
| utilities.initialize-event-repository.enabled | When set to true, the job is created. The default
value is false. |
| utilities.initialize-event-repository.maxAttempts | The maximum number of times the utility attempts to find an active processing pod on which to run the script before giving up. The default value is 100. |
| utilities.initialize-event-repository.mongodb.connectionString | This value overrides the global MongoDB connectionString. |
| utilities.initialize-event-repository.retryInterval | This is the number of seconds between each attempt to find an active processing pod on which to run the script. The default value is 20. |
| utilities.initialize-event-repository.image.nameOverride | The name to use for the image if different from the released name. |
| utilities.initialize-event-repository.image.versionOverride | The version to use for the image if different from the released version. |
| utilities.initialize-event-repository.serviceAccount.create | When set to true, the Helm chart creates the
ServiceAccount, role, and role bindings. The default value is
true. |
| utilities.initialize-event-repository.serviceAccount.name | The name of the service account to run the cron job. If
utilities.initialize-event-repository.serviceaccount.create
is set to true, the ServiceAccount is created.
Otherwise, the name must reference an existing service account with the
appropriate permissions for searching and executing on pods. The default
value is
initialize-event-repository-release_name.Important: You must first grant
permissions for the ServiceAccount. See the Red Hat OpenShift
documentation for information about setting security context
constraints. |
| utilities.initialize-event-repository.serviceAccount.annotations | Any annotations to add to the ServiceAccount. For more information, see the discussion about annotations in Kubernetes documentation. |
| utilities.initialize-event-repository.podSecurityContext | A Kubernetes security context for the pod. For more information, see the discussion about pod security contexts in Kubernetes documentation. |
| utilities.initialize-event-repository.securityContext | A Kubernetes security context for the main container in the pod. For more information, see the discussion about security contexts in Kubernetes documentation. |
| utilities.initialize-event-repository.resources | A Kubernetes resource defined for the main container in the pod. For more information, see the discussion about resources in Kubernetes documentation. |
| utilities.initialize-event-repository.nodeSelector | A Kubernetes node selector defined for the pod. For more information, see the discussion about node selectors in Kubernetes documentation. |
| utilities.initialize-event-repository.tolerations | Kubernetes tolerations assigned to the pod. For more information, see the discussion about tolerations in Kubernetes documentation. |
| utilities.initialize-event-repository.affinity | Kubernetes affinity rules assigned to the pod. For more information, see the discussion about affinity rules in Kubernetes documentation. |