Table of Contents
Before installaing and configuring Tungsten Operator a number of prerequisites need to be in place. These are outlined in the following sections.
The documentation does not provide steps for installing, configuring or managing Kubernetes clusters, or the installation of Docker. It is assumed that you have extensive knowledge of this, and in situations of uncertainty, the appropriate provider documentation should be referenced.
The operation and management of Tungsten Clusters are not covered in the chapters of this documentation. For all of the necessary operations, you should review the main Tungsten Clustering Documentation.
You will need access to a Docker Container Registry to hold the images and act as a repository (For example in GCP, an Artifact Registry).
There are no specific requirments for this, only that it is accessible from your own environment.
A pre-configured Kubernetes cluster will be needed. This documentation assumes that you have all needed knowledge and understanding for launching, managing and configuring the Kubernetes cluster before starting - steps for installation and configuration of the Kubernetes cluster are not provided here.
For full documentation for Kubernetes, please click here
However, there are a number of minimum requirements for Tungsten Operator, which should be followed, these are listed below:
The minimum Kubernetes version must be at least v1.25 (Note: Versions prior to v1.30 are EOL)
A minimum of 3 nodes are required, and ideally these should be distributed across different regions/zones.
Each pod that will act as a Tungsten Cluster node will require sufficient memory allocated based on the following minimum requirements:
Minimum 1Gb for the Tungsten Manager
Minimum 2Gb for the Tungsten Replicator
Minimum 1Gb for the Tungsten Connector
Memory allocation for MySQL based on your own MySQL database requirements.
cert-manager : Tungsten Operator has been tested and certified with versions higher than or equal to 1.16. Older versions may work, but have not been tested or certified.
A staging/admin host will be required from where you will be able to manage the deployment of Tungsten Operator and access nodes.
This section outlines the minimum requirements and configuration needed for this staging host, as follows:
Connectivity from the staging host to the cloud hosting the Kubernetes Cluster and the Docker Registry.
Docker - No specific version requirements, only that it is compatible with the version of Kubernetes in use.
kubectl - No specific version requirements, only that it is in sync with the same version of Kubernetes in use.
A configured directory for storing downloaded Tungsten images. Further
examples in this documentation use /opt/continuent/software
as this location and aligns with the recommended default for all
Tungsten software staging locations.
A non-root OS user, we recommend configuring an OS user called tungsten
OPTIONAL: kind should be installed if you wish to use the staging host to deploy small local clusters for QA and Testing.
OPTIONAL: cli tools such as those provided by AWS or GCP. These are not used during installation, however can be useful for testing connectivity