Informix SQL Data Store Configuration
To customize the installation and configurations, see the list of configuration parameters available to the Informix SQL Data Store.
List of Informix SQL Data Store Configuration Parameters
| Parameter | Description | Value |
|---|---|---|
| global.hclImagePullSecret | Your own secret with your credentials to HCL’s Docker repository. Required when deploying solution in your own cluster. | ‘’ |
| global.isOpenShift | Set to true if using Openshift | false |
| nfsserver.enabled | Set this attribute to ‘true’ to mount ReadWriteMany PVC across all Informix server pods. Required for OnBar storage space and logical log backups. If this attribute value is set to ‘false’, then rest of the “nfsserver” related helm attributes are ignored. | false |
| nfsserver.volumeSize | Size of the Volume used for backups and other shared files. | 50G |
| nfsserver.googleFilestore.enable | Set to true to enable Google Filestore | false |
| nfsserver.googleFilestore.filestoreIP | IP address of the Filestore instance | ‘’ |
| nfsserver.googleFilestore.filestoreShare | Name of the File share on the instance | ‘’ |
| nfsserver.awsEFS.enable | Set to true to enable AWS Elastic filestore | false |
| nfsserver.awsEFS.EFSServer | DNS name of the file system | fs-XXXXX.efs-us-west-2.amazonaws.com |
| nfsserver.awsEFS.EFSPath | NFS Mount path | / |
| nfsserver.azureFS.enable | Set to true to enable Azure File share | false |
| nfsserver.azureFS.secretName | Kubernetes secret name to use | ‘’ |
| nfsserver.azureFS.shareName | Azure file share name | ‘’ |
| nfsserver.other.enable | Set to true to enable | true |
| nfsserver.other.storageClass | Set this to the storageClass of the NFS | nfs |
| tls.config | Set to true to enable TLS communication | false |
| tls.tlskey | Base64 value of server private key | tlskey: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS ... |
| tls.tlscert | Base64 value of signed server certificate | tlscert: LS0tLS1CRUdJTiBDRVJUSEDFRQ0FURS ... |
| tls.tlscacert | Base64 value of certificate authority root certificate | tlscacert: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS ... |
| autoscaling.enabled | Set to true to enable auto scaling. To use auto scaling make sure to set Informix.serverReplicaCount, informix.maxReplicaCount and informix.resources appropriately. | false |
| autoscaling.targetCPUUtilizationPercentage | Set to the Percentage when autoscaling should occur. | 70 |
| Informix.serverReplicaCount | Set to the number of servers to start for an HA cluster | 2 |
| informix.maxReplicaCount | Set to the max value of servers you would want to configure in the HA cluster | 10 |
| informix.dbsapwd | Informix Server DBSA (Informixsa) user password | Informix4ever |
| informix.backupTag | Set to unique value in case the backup device is shared with other Informix HA Cluster | Informixbackup-myuniquetag |
| informix.encryptionAtRest | Set to true to enable Encryption at rest | false |
| informix.hqAgent | Set to true to start the Informix HQ Agent on each server | false |
| informix.dataStorageClass | Set to the cloud vendor default storage class. Low latency disk I/O storage is recommended. For GKE “standard” is the default | "" |
| informix.dataStorageSize | Set the persistent Volume Size | 10gi |
| informix.dataStorageCount | Number of persistent volume’s to provision | 2 |
| informix.restoreFromBackup | Set to true when a restore from last backup is needed | false |
| informix.restoreTimestamp | set to specific point in time to perform a point in time restore. Ex 2021-05-11 11:35:00 | ‘’ |
| informix.nodeSelectorRequired | Set to true to enforce that no two Informix Server pods are scheduled on the same K8s node | true |
| informix.nodeSelector | Set to a node label to schedule Informix server pods on preconfigured set of K8s nodes. Set your own keyvalue pair for the node selector | ‘’ |
| informix.tolerations | Used to assist the K8s schedule | {} |
| informix.resources | Resources like cpu and memory requested from the cluster. | {} |
| informix.customServerEnv | Allows you to set additional environment variables to be used by the database server. | ‘’ |
| informix.customConfig | Allows you to set ONCONFIG parameters to be used by the Database server. | MULTIPROCESSOR: 1 |
| informix.customSpace | Allows you to create custom Dbspaces in the database server | ‘’ |
| informix.appUsers | Allows you to create custom Users in the database server | ‘’ |
| informix.customInitSQL | Allows you to create a script of SQL statements that is run after server initialization. | ‘’ |
| informix.customInitImage | Allows you to create an Init Container image | ‘’ |
| informix.customInitImageCmd | The command to run from the custom Init container | ‘’ |
| informix.groupName | Unique name for each cluster if Setting up Enterprise Replication | g_cdr1 |
| informix.groupID | Unique ID for each cluster if setting up Enterprise Replication | 1 |
| informix.updateStrategyType |
This attribute controls Informix server statefulset update strategy. Supported values are “RollingUpdate” and “OnDelete”. OnDelete With OnDelete update strategy, the StatefulSet controller will not automatically update the Pods in a StatefulSet. Users must manually delete Pods to cause the controller to create new Pods that reflect modifications made to a StatefulSet. RollingUpdate The RollingUpdate update strategy implements automated, rolling update for the Pods in a StatefulSet. This is the default update strategy. The RollingUpdate process will start from the highest pod ordinal index to the lowest pod ordinal index. For example, Informix-server-1 is updated before Informix-server-0. |
RollingUpdate |
| informixcmReplicaCount | Number of Connection Managers to start for the HA cluster | 2 |
| informixcm.serviceType | Set the service type of the connection manager. (ClusterIP, LoadBalancer or NodePort) | ClusterIP |
| informixcm.sla_policy | Set the service level agreement of the connection manager. (ROUNDROBIN, WORKLOAD) | ROUNDROBIN |
| informixcm.autofailover | If set to false then autofailover is disabled | true |
| informixcm.nodeSelectorRequired | Set to true to enforce that no two Informix CM pods are scheduled on the same K8s node. | true |
| informixcm.nodeSelector | Set to a node label to schedule Informix pods on preconfigured set of K8s nodes. Set your own keyvalue pair. | ‘’ |
| informixcm.tolerations | Used to assist the K8s schedule | {} |
| informixcm.resources | Resources like cpu and memory, requested from the cluster | {} |
| informixcm.updateStrategyType |
This attribute controls Informix Connect (Connection Manager) statefulset update strategy. Supported values are “RollingUpdate” and “OnDelete”. OnDelete With OnDelete update strategy, the StatefulSet controller will not automatically update the Pods in a StatefulSet. Users must manually delete Pods to cause the controller to create new Pods that reflect modifications made to a StatefulSet. RollingUpdate The RollingUpdate update strategy implements automated, rolling update for the Pods in a StatefulSet. This is the default update strategy. The RollingUpdate process will start from the highest pod ordinal index to the lowest pod ordinal index. For example, informixcm-1 is updated before informixcm-0. |
RollingUpdate |