About Using the ttclassic Helm Chart
The ttclassic
Helm chart contains the information needed to deploy replicated and non-replicated TimesTen database in your Kubernetes namespace. There are many customizations available to meet your preferred configuration. There are variables specific to the ttclassic
chart for such customizations. The About Creating TimesTen Databases section discusses some of these customizations. For additional customizations, see The ttclassic Chart.
testUser
. After TimesTen is deployed, you can use the helm
test
command to test TimesTen. The test operation requires that a TimesTen test
user exist in the TimesTen database. This user connects to the database as part of the testing process. This user must be defined before installing the ttclassic
chart. The TimesTen Operator provides the testUser
metadata file for this purpose. The file contains one line of the form:testuser/testuserpassword
where testuser
is the name of the TimesTen user to use for testing TimesTen and testuserpassword
is the password for this test
user. For details, see Use Configuration Metadata.
If you are using Kubernetes ConfigMaps or Secrets as the facilities to place metadata files into the TimesTen containers, you do not need to create them. Instead, when you install the ttclassic
chart, the ConfigMaps and Secrets are automatically created as part of the installation process. To facilitate the process, you must create a directory within the ttclassic
chart directory tree and create the metadata files in this directory. There are examples later in this section that show you how to do this.
ttclassic
chart's installation process:
-
Create a YAML file for the variables. When installing the
ttclassic
chart, pass this YAML file to thehelm
install
command by specifying the-f
option. -
Specify the variables on the command line by running the
helm
install
command with the--set
option.
The examples use a YAML file. For specifics about these options including the syntax, see https://helm.sh/docs/intro/using_helm/ in the Helm documentation.
The examples show you how to use the ttclassic
Helm chart to define and deploy replicated and non-replicated TimesTen databases. Both examples use the same set of metadata files and both use Kubernetes ConfigMaps to get the metadata files into the tt
containers.
For simplicity, let's create the metadata files and ConfigMaps used in the examples. For complete details about metadata files, see Use Configuration Metadata and Populate the /ttconfig Directory.