What's New

This section summarizes the new features of Oracle TimesTen In-Memory Database Release 22.1 that are documented in this guide. It provides links to more information.

New Features in Release 22.1.1.34.0

• In previous releases, you could install the TimesTen Operator in one or more namespaces in your Kubernetes cluster at namespace-scope. In this release, you also have the option to install the TimesTen Operator in the timesten-operator namespace at cluster-scope. Specifically, you now have two options for installing the TimesTen Operator. See About the TimesTen Operator.

• To optimize client/server performance, the TimesTen Operator creates NodePort Services and provides a new feature, called the Connection Manager. The Connection Manager functions as an https server. It adds several new endpoints to the /metrics server. These new endpoints allow client/server applications to retrieve a connection string that can then be used to access TimesTen databases optimally. See Optimize Client/Server Performance. The TimesTen Operator provides the following syntax for the Connection Manager:

  • If you are using YAML manifest files to install the TimesTen Operator, see the TT_CONNECTION_MANAGER, TT_CONNECTION_MANAGER_NODEPORT, and TT_OPERATOR_SAN environment variables in TimesTen Kubernetes Operator Environment Variables.

  • If you are using either the ttoperator or ttclusteroperator Helm chart to install the TimesTen Operator, see connectionManager, operatorNodePort, and operatorSAN in The ttoperator Chart or The ttclusteroperator Chart.

• The TimesTen Operator can automatically create self-signed certificates and configure TimesTen to use those certificates for client/server TLS encryption. See Automatically Configure Client/Server TLS. The TimesTen Operator provides the following syntax for this feature:

  • If you are using YAML manifest files, see clientTLS in TimesTenClassicSpecSpec.

  • If you are using Helm charts, see clientTLS in The ttclassic Chart.

• You can set the number of TimesTenClassic objects that the TimesTen Operator processes concurrently:

  • If using YAML manifest files to install the TimesTen Operator, see the TT_MAX_RECONCILES environment variable in TimesTen Kubernetes Operator Environment Variables.

  • If you are using either the ttoperator or ttclusteroperator Helm chart to install the TimesTen Operator, see maxReconciles in The ttoperator Chart or The ttclusteroperator Chart.

• The TimesTen Operator adds a default security context, including the Kubernetes default seccomp profile to the Pods it creates. In addition, the TimesTen Operator runs with a default security context and includes the Kubernetes default seccomp profile. See About the Default Kubernetes Security Context for TimesTen Pods and About the Default Kubernetes Security Context for the TimesTen Operator.

• By default, the TimesTen Operator adds affinity and anti-affinity settings to Pods that are created when deploying a TimesTenClassic object. See About the Default Affinity and Anti-Affinity Settings for TimesTenClassic Objects.

• The TimesTen Operator stores its security certificates in Java Keystores. In order to create and use Java Keystores, they must be secured with a known password:

  • If you are using YAML manifest files, see storePassword in TimesTenClassicSpecSpec.

  • If you are using Helm charts, see storePassword in The ttclassic Chart.

• There is support for the v4 schema version of the TimesTenClassic Custom Resource Definition (CRD). The v2 schema version of the TimesTenClassic CRD is deprecated. The v2 schema version is fully supported in this release, but will be removed in a future release. See About TimesTen CRDs.

New Features in Release 22.1.1.30.0

• For non-replicated configurations, you can increase or decrease the number of databases deployed in your Kubernetes namespace. To make this change, modify the number of replicas associated with one or more of your TimesTenClassic objects. See Modify the Number of Replicas in Non-Replicated Environments.

• In both replicated and non-replicated configurations, the TimesTen Operator can detect and take action in situations where a Kubernetes Node is not ready (or unknown) for a specific period of time. To direct the TimesTen Operator to detect and take action, specify the .spec.ttspec.deleteDbOnNotReadyNode datum in a TimesTenClassic object definition. See How the TimesTen Kubernetes Operator Handles Node Failure and About Specifying the .spec.ttspec.deleteDbOnNotReadyNode Datum.

  In order to use this feature, the TimesTen Operator requires additional privileges and permissions. See Install the TimesTen Operator at Namespace-Scope.

• The TimesTen Operator generates the following new metrics:

  • timesten_pods_deleted_unschedulable

  • timesten_pods_unschedulable

  • timesten_pvcs_deleted_unschedulable

    For more information, see About Kubernetes Events and TimesTen Operator Metrics.

• The v1 schema version of the TimesTenClassic Custom Resource Definition (CRD) is deprecated. The v1 schema version is fully supported in this release, but will be removed in a future release. For more information, see About TimesTen CRDs.

New Features in Release 22.1.1.27.0

• The TimesTen Kubernetes Operator (TimesTen Operator) provides full support for non-replicated TimesTenClassic objects. Databases in this configuration operate independently and have no relationship to each other:

  • The TimesTen Operator creates, manages, and monitors TimesTenClassic objects and associated databases in this configuration. See Create TimesTen Classic Databases.

  • There is full support for upgrading (and downgrading) non-replicated TimesTenClassic objects to a new patch or patchset. See About Upgrading TimesTen Classic Databases.

  • There are TimesTen Operator metrics for monitoring the overall status of non-replicated TimesTenClassic objects. See TimesTen Kubernetes Operator Metrics.

  • The TimesTen Operator provides and maintains high level states for TimesTenClassic objects and TimesTen Pods in non-replicated configurations. These states describe the health of TimesTenClassic objects and the health of TimesTen databases in Pods. See About the High Level State of TimesTenClassic Objects and About the High Level State of TimesTen Pods.

• There are metrics for monitoring the memory used by the TimesTen Operator and the TimesTen Agent. See TimesTen Kubernetes Operator Metrics.

• The TimesTen Operator uses Kubernetes Custom Resource Definition (CRD) versioning to provide two different schema versions for the TimesTenClassic CRD. The TimesTen Operator creates, monitors, and manages TimesTenClassic objects in both schema versions. See About TimesTen CRDs.

• The TimesTen Operator provides and enables by default readiness probes for TimesTen containers in replicated and non-replicated configurations. See About Readiness Probes for TimesTen Containers.

• The TimesTen Operator runs in single and multi-architecture Kubernetes clusters. Pods that are created by the TimesTen Operator run on nodes of the same node type as the TimesTen Operator. For example, if the TimesTen Operator runs on arm64 nodes, Pods created by this TimesTen Operator also run on arm64 nodes. If you are using a multi-architecture Kubernetes cluster, you have to make customizations to the provided operator.yaml YAML manifest file and the ttoperator Helm charts. See About Deploying in a Multi-Architecture Kubernetes Cluster.

• TimesTen provides an additional option for obtaining container images that you can use in your TimesTen Kubernetes Operator environment. You can use the Oracle TimesTen In-Memory Database for Kubernetes - BYOL on Oracle Cloud Marketplace container listing to export a TimesTen container image into a repository in Oracle Cloud Infrastructure Registry (Container Registry). See Prepare to Use the TimesTen Kubernetes Operator.

• To support the new features, the .spec.ttspec section of the TimesTenClassic object type includes the following datum:

  • createASReadinessProbe

  • readOnlyRootFilesystem

  • replicas

  • replicationTopology

  • rollingUpdatePartition

  • terminationGracePeriod

  See TimesTenClassicSpecSpec.

• Helm and the associated ttcrd, ttoperator, and ttclassic Helm charts are extended to support the new features. See Use Helm in Your TimesTen Kubernetes Operator Environment and Helm Charts for the TimesTen Kubernetes Operator.

New Features in Release 22.1.1.19.0

• The TimesTen Kubernetes Operator (TimesTen Operator) provides TimesTen-specific Helm charts. These charts let you use Helm to install the TimesTen CRDs, TimesTen Operator, and TimesTenClassic objects in your Kubernetes cluster. See Use Helm in Your TimesTen Kubernetes Operator Environment.

• By default, the TimesTen Operator automatically exports and exposes TimesTen metrics to Prometheus. See Expose TimesTen Metrics with the TimesTen Kubernetes Operator.

  You can control how TimesTen metrics are exported and exposed by using specific datum in your TimesTenClassic and TimesTenScaleout object YAML manifest files. See About Exposing TimesTen Metrics and TimesTenClassicSpecSpecPrometheus and TimesTenScaleoutSpecSpecPrometheus.

• The TimesTen Operator automatically exposes metrics about its own functionality as well as the status of TimesTenClassic and TimesTenScaleout objects that it manages to Prometheus. See Expose Metrics from the TimesTen Kubernetes Operator.

  You can control how these metrics are exposed by unsetting or setting TimesTen Operator environment variables located in the operator.yaml YAML manifest file of your TimesTen Operator deployment. See About Exposing Metrics from the TimesTen Kubernetes Operator and TimesTen Kubernetes Operator Environment Variables.

• The TimesTen Operator provides readiness and liveness probes so that Kubernetes can determine the health of the TimesTen Operator. See About Readiness and Liveness Probes.

• The TimesTen Operator creates and manages readiness probes for TimesTen containers. See About Readiness Probes for TimesTen Containers.

New features in Release 22.1.1.9.0

• The TimesTen Operator monitors and manages TimesTen Scaleout objects that are deployed in your Kubernetes cluster. It also detects, repairs, and recovers from failures in your grid and associated database. See Manage TimesTen Scaleout.

• The Operator supports TimesTen Cache in TimesTen Scaleout. See Work with TimesTen Cache.

• It is essential to specify memory requests and limits to Kubernetes. TimesTen recommends that CPU requests and limits be specified as well. See Specify CPU and Memory Requests and Limits. To support this functionality, there are new datum added to the .spec.ttspec fields of the TimesTenClassic and TimesTenScaleout object custom resource definitions. See TimesTenClassicSpecSpec and TimesTenScaleoutSpecSpec.

• TimesTen container images use the Oracle Linux base image. Oracle Java is installed into the TimesTen images using JDK script friendly URLs and Dockerfile techniques. For details about setting up your environment, see Prepare to Use the TimesTen Kubernetes Operator. For specific information about TimesTen container images, see About TimesTen Container Images and Container Registry Options. For information about Dockerfile ARGS, see Dockerfile ARGs.

New features in Release 22.1.1.3.0

• The TimesTen Operator can deploy TimesTen Scaleout grids and their associated TimesTen databases in your Kubernetes cluster. See Deploy TimesTen Scaleout Databases.

  The TimesTen Operator supports the TimesTenScaleout object type. This object type provides the syntax you need to deploy a TimesTen Scaleout grid and database. See About the TimesTenScaleout Object Type.

• In previous releases, the TimesTen Operator required the creation of two container images, one for the Operator and one for TimesTen. In this release, one container image is used for both the Operator and TimesTen. You can create this container image or pull it from the Oracle Container Registry at container-registry.oracle.com. See Prepare to Use the TimesTen Kubernetes Operator.

• When using the TimesTen Operator, the name of the Linux user that is created in the container image is timesten with a numeric UID of 3429. The name of the Linux group that is created in the container image is timesten with a GID of 3429. The timesten user is the user who runs TimesTen and the timesten group is the TimesTen users group. You can override these defaults. This lets you tailor attributes of the image to meet your requirements. See Dockerfile ARGs.

• The TimesTen Operator supports the TimesTen Prometheus Exporter. You can configure your TimesTenClassic and your TimesTenScaleout objects to use the Exporter. The Exporter can then collect metrics from the TimesTen databases that are running in your Kubernetes cluster, and expose these metrics to Prometheus. See Create Your Own Oracle Wallet, Certificates, and Secrets for Exposing TimesTen Metrics.

  The TimesTen Operator provides the prometheus object type as part of the TimesTenClassic and TimesTenScaleout object type definitions. Use the prometheus object type to configure the Exporter to meet your Prometheus requirements. See TimesTenClassicSpecSpecPrometheus and TimesTenScaleoutSpecSpecPrometheus.

New features in Release 22.1.1.1.0

You can define a readiness probe to tell Kubernetes that a TimesTen (tt) container is ready. See About Readiness Probes for TimesTen Containers.