Prerequisites to Deploy the TimesTen Operator

Before you create a stack to deploy the TimesTen Operator:

• You must have access to an OCI tenancy. The tenancy must be subscribed to one or more of the regions in which OKE is available. See Availability by Region.

• Your tenancy must have sufficient quota on:

  • Compute instance quota: The compute instance quota depends on the shape you select. Compute instance quota is determined by the compute cores and the amount of memory required for a particular shape. There should be enough quota for the specified number of worker nodes in the specified shape for the managed node pool for TimesTen databases. See Compute Limits.

  • Block volume quota: The TimesTen Operator creates a persistent volume claim (PVC) for each worker node containing a TimesTen database. Persistent volume claims must request a minimum of 50 gigabytes. See Setting Up Storage for Kubernetes Clusters.

  • Bastion quota: The stack creates a temporary bastion to access the OKE cluster, if necessary. There should be enough quota for at least one bastion. See Bastion Limits.

• Within your tenancy, there must already be an OKE cluster for managed node pools. See Creating Kubernetes Clusters Using Console Workflows.

  • The stack deploys the TimesTen Operator in a namespace at namespace scope. The stack configuration page requires that you provide a namespace for the TimesTen Operator and TimesTen databases. This namespace must be already configured in the OKE cluster before launching the stack. See About the TimesTen Operator in Oracle TimesTen In-Memory Database Kubernetes Operator User's Guide and Namespaces.

  • The stack configuration page requires that you provide a Kubernetes Secret with the credentials for Oracle Container Registry. For this, you must have access to an Oracle Container Registry account. To deploy the TimesTen Operator, the stack pulls the latest TimesTen container image from Oracle Container Registry using the provided Secret. See Example 2-1.

    You must agree to and accept the Oracle Standard Terms and Restrictions for downloading official container images of Oracle TimesTen In-Memory Database from Oracle Container Registry before launching the stack. To agree to and accept the Oracle Standard Terms and Restrictions, do the following:

    1. On the Oracle Container Registry homepage, click on TimesTen.
    2. On the TimesTen Repositories page, click Continue for the timesten repository.
    3. Read and understand the terms set by the Oracle Standard Terms and Restrictions pop-up, then click Accept.

• Within your tenancy, there must already be a compartment that contains the necessary network resources, such as:

  • VCN

  • Subnets

  • Internet gateway

  • NAT gateway

  • Service gateway

  • Route table

  • Security lists

  These resources must be configured in the region in which you want to deploy TimesTen databases. These resources can be the same as those used by the OKE cluster. See Network Resource Configuration for Cluster Creation and Deployment.

• Within your tenancy, there must already be a compartment to contain the stack. This compartment can be the same as the one associated with the OKE cluster.

• To create and manage the stack and OKE cluster, you must belong to one of the following:

  • The Administrators group of the tenancy.

  • A group to which a policy grants the appropriate Marketplace and OKE permissions. See Required IAM Policies to Deploy the TimesTen Operator.

• You must have a development host to access the OKE cluster. The host can be a virtual machine (VM) instance in the same tenancy as your cluster. Ensure that:

  • The host resides outside the OKE cluster.

  • The host is able to access and control the OKE cluster. For this, ensure that the podman (or docker) and kubectl command line tools are installed on the host. See the Podman and kubectl documentation.

    The stack uses Helm to deploy the TimesTen Operator and most of the examples in this guide use Helm. To be able to follow the examples, ensure that the helm command line tool is also installed. See the Helm documentation.

  See Setting Up Cluster Access.

Example 2-1 Creating a Kubernetes Secret to Oracle Container Registry

This example creates a Kubernetes Secret to Oracle Container Registry (OCR).

1. From your development host, log in to OCR,

   podman login container-registry.oracle.com

   1. When prompted for a user name, enter your username for OCR.

   2. When prompted for a password, enter your auth token for your OCR username.

2. Create a Kubernetes Secret in the namespace you designated for the TimesTen Operator with the credentials stored in your authentication file.

   kubectl create secret generic <secret-name> \
     --from-file=.dockerconfigjson=<path> \
     --type=kubernetes.io/dockerconfigjson \
     --namespace <namespace>

   Note:

   The default path for the authentication file is ${XDG_RUNTIME_DIR}/containers/auth.json on Linux and $HOME/.config/containers/auth.json on Windows or macOS.