Launch the Stack to Deploy the TimesTen Operator

To deploy the TimesTen Operator from the stack listing on Marketplace:

1. Sign in to your tenancy in Oracle Cloud Console (Console).
2. In the top-left corner of the Console, expand the Navigation menu and click Marketplace. Then, click All Applications.
3. Click on the Oracle TimesTen In-Memory System of Record for Oracle Cloud Infrastructure Kubernetes Engine-x86 stack listing.
   To find the listing, you may use the filters and search bar as follows:
   1. In Filters, in the Type drop-down list, select Stack.
   2. In the Publisher drop-down list, select Oracle.
   3. In the Price drop-down list, select Paid.
   4. To narrow your search even further, in the search bar, type TimesTen.
4. In the Version drop-down list, select the version that matches the Kubernetes version of your OKE cluster.
5. In the Compartment drop-down list, select a compartment with the appropriate IAM policies.
   This is the compartment where the stack will be created. See Required IAM Policies to Deploy the TimesTen Operator.
6. Review and accept the Oracle Standard Terms and Restrictions.
7. Click Launch Stack.
8. (Optional) Provide a name for the stack.
9. (Optional) Provide a description for the stack.
10. Click Next.
11. In OKE cluster configuration, select the compartment of your OKE cluster.
12. Select your OKE cluster.
13. Specify the namespace for the TimesTen Operator and TimesTen databases.
    This namespace must already exist in the OKE cluster.
14. Specify the Kubernetes Secret with the credentials for Oracle Container Registry.
    The Secret must already exist in the OKE cluster.
15. In Worker nodes configuration, provide the name for the node pool to be created for TimesTen databases.
    Due to license restrictions, TimesTen databases can only be created in the worker nodes from this node pool.
16. Select the shape of the worker nodes.
    Since TimesTen is an in-memory database, select a shape that provides as much memory as required by the data and workloads intended for the TimesTen databases.
17. Specify the boot volume size for each worker node.
    The size of the boot volume should be enough to store all TimesTen-related files.
18. Specify the number of worker nodes.
    For high availability, it is recommended that each TimesTen database uses its own worker node. For example, an active standby pair replication scheme consists of two TimesTen databases, an active and standby. For this configuration, a minimum of two worker nodes is recommended.
19. In Network and placement configuration, provide the compartment of the VCN used by the OKE cluster.
20. Select the name of the VCN.
21. Select the name of the subnet used by any existing worker nodes in the OKE cluster.
    Ensure that you do not specify the subnet used for the Kubernetes API endpoint. Otherwise, deployment of the worker nodes of the new node pool fails.
22. Either upload the SSH public key file or paste the SSH public key for SSH access to the worker nodes.
23. In Pod networking configuration, select the subnet that the Pods for TimesTen databases should use.
    Ensure that you do not specify the subnet used for the Kubernetes API endpoint. Otherwise, deployment of the worker nodes of the new node pool fails.
24. Click Next.
25. Verify all the configuration variables.
26. Select the Run apply checkbox.
    This ensures that the required resources are provisioned immediately and starts the deployment of the TimesTen Operator and the creation of the node pool for TimesTen databases.
27. Click Create.

This operation is asynchronous. To monitor its progress, check the job details for the stack in Resource Manager. See Getting a Job's Details.