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.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 to Deploy the TimesTen Kubernetes Operator and TimesTenClassic Objects.

• 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. For a complete example, see TimesTen Cache in TimesTen Scaleout Example.

• 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 Set Up the Environment. For specific information about TimesTen container images, see About TimesTen Container Images. 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 Set Up the Environment.

• 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 Option 2b: Build with Customizations and 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.