diff --git a/Chart.yaml b/Chart.yaml index 7cb7f7c..188c9e8 100644 --- a/Chart.yaml +++ b/Chart.yaml @@ -15,7 +15,7 @@ apiVersion: v2 name: vertica-kafka-scheduler description: Deploys the Vertica Kafka Scheduler in Kubernetes type: application -version: 0.1.7 +version: 0.1.8 # The appVersion corresponds to the Vertica version appVersion: "24.1.0" icon: https://raw.githubusercontent.com/vertica/kafka-scheduler-chart/main/vertica-logo.png diff --git a/README.md b/README.md index 1eecbc0..5a226e4 100644 --- a/README.md +++ b/README.md @@ -344,6 +344,10 @@ Now that you have a containerized Kafka cluster and VerticaDB CR running, you ca
serviceAccount.name
Name of the service account. If this parameter is not set and serviceAccount.create is set to true, a name is generated using the fullname template.
+
timezone
+
Utilize this to manage the timezone of the logger. As logging employs log4j, ensure you use a Java-friendly timezone ID. Refer to this site for available IDs: https://docs.oracle.com/middleware/1221/wcs/tag-ref/MISC/TimeZones.html
+
Default: UTC
+
tls.enabled
When set to true, the scheduler is set up for TLS authentication.
Default: false
diff --git a/templates/configmap.yaml b/templates/configmap.yaml index 4130f96..ed65838 100644 --- a/templates/configmap.yaml +++ b/templates/configmap.yaml @@ -17,7 +17,7 @@ data: - %d{yyyy-MM-dd HH:mm:ss.SSS} [%X{PID}:%t] %logger::%t %X{tuple} [%p] %m%n + %d{yyyy-MM-dd HH:mm:ss.SSS}{{ printf "{%s}" .Values.timezone }} [%X{PID}:%t] %logger::%t %X{tuple} [%p] %m%n diff --git a/values.schema.json b/values.schema.json index 9afbd3e..c2dea04 100644 --- a/values.schema.json +++ b/values.schema.json @@ -152,6 +152,11 @@ "description": "Controls the setting of VKCONFIG_JVM_OPTS in the pods. Values for truststore and keystore are added automatically based on the tls.* values", "type": "string" }, + "timezone": { + "description": "Utilize this to manage the timezone of the logger. As logging employs log4j, ensure you use a Java-friendly timezone ID. Refer to this site for available IDs: https://docs.oracle.com/middleware/1221/wcs/tag-ref/MISC/TimeZones.html", + "type": "string", + "default": "UTC" + }, "serviceAccount": { "type": "object", "additionalProperties": false, diff --git a/values.yaml b/values.yaml index 7a83d39..f63468a 100644 --- a/values.yaml +++ b/values.yaml @@ -99,6 +99,11 @@ tls: # and keystore are added automatically based on the tls.* values. jvmOpts: "" +# Utilize this to manage the timezone of the logger. As logging employs log4j, +# ensure you use a Java-friendly timezone ID. Refer to this site for available +# IDs: https://docs.oracle.com/middleware/1221/wcs/tag-ref/MISC/TimeZones.html +timezone: UTC + serviceAccount: # Specifies whether a service account should be created create: true