Before You Begin

This example assumes that the TimesTenClassic CRD is deployed in your Kubernetes cluster and the TimesTen Operator is running in your namespace at namespace-scope. The example also assumes you have created metadata files and created a Kubernetes Configmap for these metadata files.

Let's confirm the TimesTenClassic CRD is deployed and the TimesTen Operator is running. Next, let's create some metadata files and create a Configmap for these metadata files. These metadata files and their content are not required for automatically configuring client/server TLS. They are used for explanatory purposes.

1. Confirm the TimesTenClassic CRD exists in your Kubernetes cluster.

   kubectl get crds | grep timesten

   The output is similar to the following:

   timestenclassics.timesten.oracle.com               2025-03-28T16:34:33Z

2. Confirm the TimesTen Operator is running in your namespace at namespace-scope.

   kubectl get pods

   The output is similar to the following:

   NAME                                 READY   STATUS    RESTARTS   AGE
   timesten-operator-79bddcc446-nktcz   1/1     Running   0          3m54s

3. Create the metadata files.
   1. From a directory of your choice, create an empty subdirectory for the metadata files. This example creates the cm subdirectory.

      mkdir cm

   2. Using an editor of your choice, create your desired metadata files. Exit from your editor after creating each file.

      db.ini:

      vi cm/db.ini
      
      PermSize=200
      DatabaseCharacterSet=AL32UTF8

      adminUser:

      vi cm/adminUser
      
      adminuser/adminuserpwd

      schema.sql

      vi cm/schema.sql
      
      create table adminuser.emp (id number not null primary key, name char (32));

4. Create a Kubernetes Configmap for the metadata files.
   1. Create the configmap.

      kubectl create configmap sampletls --from-file cm

   2. (Optional) Review the Configmap in your namespace.

      kubectl describe configmap sampletls

      The output is similar to the following:

      Name:         sampletls
      Namespace:    mynamespace
      Labels:       <none>
      Annotations:  <none>
      
      Data
      ====
      adminUser:
      ----
      adminuser/adminuserpwd
      
      db.ini:
      ----
      PermSize=200
      DatabaseCharacterSet=AL32UTF8
      
      schema.sql:
      ----
      create table adminuser.emp (id number not null primary key, name char (32));
      
      
      BinaryData
      ====
      
      Events:  <none>

You are now ready to perform the steps to have the TimesTen Operator automatically configure client/server TLS encryption.