23 TimesTen Kubernetes Operator Environment Variables

There are environment variables for the TimesTen Operator. The operator.yaml and cluster_operator.yaml files contain these environment variables. You can change the default setting for these environment variables depending on your needs. For more information about the TimesTen Operator, see About the TimesTen Operator.

The following table describes these variables:

Table 23-1 TimesTen Operator Environment Variables

Environment Variable	Description
CREATE_SERVICEMONITOR	Determines if the TimesTen Operator creates a Kubernetes ServiceMonitor object. Valid values are as follows: "1" (default): The TimesTen Operator should create a ServiceMonitor object. "0": The TimesTen Operator should not create a ServiceMonitor object. If EXPOSE_METRICS is set to "0" and CREATE_SERVICEMONITOR is set to "1" (default), CREATE_SERVICEMONITOR is treated as though it was set to "0". See Expose Metrics from the TimesTen Kubernetes Operator.
EXPOSE_METRICS	Determines if TimesTen Operator metrics are exposed outside of the TimesTen Operator's Pods. Valid values are as follows: "1" (default): Metrics should be exposed outside of the TimesTen Operator's Pods. "0": Metrics should not be exposed outside of the TimesTen Operator's Pods. If EXPOSE_METRICS is set to "0" and CREATE_SERVICEMONITOR is set to "1" (default), CREATE_SERVICEMONITOR is treated as though it was set to "0". In addition, if EXPOSE_METRICS is set to "0", the value of METRICS_SCHEME is ignored and http is always used. See Expose Metrics from the TimesTen Kubernetes Operator.
EXPOSE_PROBES	Determines if liveness probes should be exposed outside of the TimesTen Operator's Pods. Valid values are as follows: "1" (default): Probes should be exposed. "0": Probes should not be exposed.
JAVA_HOME	Specifies the location where Java is installed in the TimesTen container image. Default: /usr/java/jdk-21. If you are using a different location, change the value for this environment variable.
METRICS_SCHEME	Determines if TimesTen Operator metrics should be made available by https or http. Valid values are as follows: "https" (default): https is used. "http": http is used. If EXPOSE_METRICS is set to "0", the value of METRICS_SCHEME is ignored and http is always used. See Expose Metrics from the TimesTen Kubernetes Operator.
TT_CONNECTION_MANAGER	Determines if the TimesTen Operator's Connection Manager is enabled. Valid values are as follows: "1" (default): Enable the Connection Manager. "0": Do not enable the Connection Manager. If you disable metrics for the TimesTen Operator or you do not use https for metrics, the Connection Manager is not enabled. For example, if you set METRICS_SCHEME to "http" or EXPOSE_METRICS to "0", then TT_CONNECTION_MANAGER is ignored and treated as "0". See About the Connection Manager.
TT_CONNECTION_MANAGER_NODEPORT	Determines the port number on which the Connection Manager is available to applications outside of the Kubernetes cluster. The Connection Manager can be accessed from outside the Kubernetes cluster on any node in the Kubernetes cluster by this port number. The default is 32625. Valid values are between 30000 and 32767. Use this environment variable to change the port number.
TT_MAX_RECONCILES	Determines how many TimesTenClassic objects the TimesTen Operator processes concurrently. Valid values are as follows: "2" (default): The TimesTen Operator processes at most two TimesTenClassic objects at one time (in parallel). "1": The TimesTen Operator processes at most one TimesTenClassic object at one time. For performance purposes, we recommend that you do not change the default value.
TT_OPERATOR_SAN	Adds subject alternate names (SANs) to the TLS certificate that the TimesTen Operator creates to control access to the TimesTen Operator metrics and to the Connection Manager. If you use metrics and the Connection Manager from inside the Kubernetes cluster, you do not need to set this environment variable. If you use either metrics or the Connection Manager (or both) from outside the Kubernetes cluster, you must define a SAN for the nodes in the cluster. A SAN value can be a DNS name (potentially wildcarded) or an IP address. The value is a comma delimited list of SAN values, such as "1.2.3.4,1.2.3.5,*.mycluster.example.org". You can specify a single level of wildcards. By default, there is no SAN specified.