Kafka scheduler parameters

The following list describes the available settings for the Vertica Kafka Scheduler:

affinity

Applies affinity rules that constrain the scheduler to specific nodes.

conf.configMapName

Name of the ConfigMap to use and optionally generate. If omitted, the chart picks a suitable default.

conf.content

Set of key-value pairs in the generated ConfigMap. If conf.generate is false, this setting is ignored.

conf.generate

When set to true, the Helm chart controls the creation of the vkconfig.conf ConfigMap.

Default: true

fullNameOverride

Gives the Helm chart full control over the name of the objects that get created. This takes precedence over nameOverride.

initializerEnabled

When set to true, the initializer pod is created. This can be used to run any setup tasks needed.

Default: true

image.pullPolicy

How often Kubernetes pulls the image for an object. For details, see Updating Images in the Kubernetes documentation.

Default: IfNotPresent

image.repository

The image repository and name that contains the Vertica Kafka Scheduler.

Default: opentext/kafka-scheduler

image.tag

Version of the Vertica Kafka Scheduler. This setting must match the version of the Vertica server that the scheduler connects to.

For a list of available tags, see opentext/kafka-scheduler.

Default: Helm chart's appVersion

imagePullSecrets

List of Secrets that contain the required credentials to pull the image.

launcherEnabled

When set to true, the Helm chart creates the launch deployment. Enable this setting after you configure the scheduler options in the container.

Default: true

jvmOpts

Values to assign to the VKCONFIG_JVM_OPTS environment variable in the pods.

Note

You can omit most truststore and keystore settings because they are set by tls.* parameters.

nameOverride

Controls the name of the objects that get created. This is combined with the Helm chart release to form the name.

nodeSelector

nodeSelector that controls where the pod is scheduled.

podAnnotations

Annotations that you want to attach to the pods.

podSecurityContext

Security context for the pods.

replicaCount

Number of launch pods that the chart deploys.

Default: 1

resources

Host resources to use for the pod.

securityContext

Security context for the container in the pod.

serviceAccount.annotations

Annotations to attach to the ServiceAccount.

serviceAccount.create

When set to true, a ServiceAccount is created as part of the deployment.

Default: true

serviceAccount.name

Name of the service accountt. If this parameter is not set and serviceAccount.create is set to true, a name is generated using the fullname template.

timezone

Manages the timezone of the logger. As logging employs log4j, ensure you use a Java-friendly timezone ID. For details, see this Oracle documentation.

Default: UTC

tls.enabled

When set to true, the scheduler is set up for TLS authentication.

Default: false

tls.keyStoreMountPath

Directory name where the keystore is mounted in the pod. This setting controls the name of the keystore within the pod. The full path to the keystore is constructed by combining this parameter and tls.keyStoreSecretKey.

tls.keyStorePassword

Password that protects the keystore. If this setting is omitted, then no password is used.

tls.keyStoreSecretKey

Key within tls.keyStoreSecretName that is used as the keystore file name. This setting and tls.keyStoreMountPath form the full path to the key in the pod.

tls.keyStoreSecretName

Name of an existing Secret that contains the keystore. If this setting is omitted, no keystore information is included.

tls.trustStoreMountPath

Directory name where the truststore is mounted in the pod. This setting controls the name of the truststore within the pod. The full path to the truststore is constructed by combining this parameter with tls.trustStoreSecretKey.

tls.trustStorePassword

Password that protects the truststore. If this setting is omitted, then no password is used.

tls.trustStoreSecretKey

Key within tls.trustStoreSecretName that is used as the truststore file name. This is used with tls.trustStoreMountPath to form the full path to the key in the pod.

tls.trustStoreSecretName

Name of an existing Secret that contains the truststore. If this setting is omitted, then no truststore information is included.