Watch the 7.3 Webinar On-Demand
This new release brings updates to Universal Storage, query optimization, and usability that you won’t want to miss.
The changelog for the MemSQL Operator is listed here. To learn how to use the Operator, see the Kubernetes deployment guide.
SingleStore’s Docker images can be found on Docker Hub.
rootuser. The default resource pool associated with that user will be used in the backup job.
|Docker Hub Image|
rootServiceUserflag in the CR to control whether to grant
priorityClassNamevia an Operator command-line parameter
priorityClassNamewill be passed to all StatefulSet’s PodSpec.
backup-compatibility-modethat were inadvertently removed from the Operator 1.2.0 release. Refer to the Backups reference for more information.
backup-compatibility-modecommand-line parameters. Refer to the Backups reference for more information.
globalVariablessection in the CR. Refer to List of Engine Variables for more information. Adding, removing, or updating engine variables will cause pods to restart. The following variables are explicitly prohibited:
phasefield to CR status.
Runningindicates that the Operator is happy with the state of the cluster and that there are no more changes to be made.
Pendingindicates that the Operator is still working towards a desired state of the cluster.
monitoringSpecin the CR to allow MemSQL to be configured to push metrics to Kafka.
cgroup-aware and respect container resource boundaries for containerized deployments.
glibctunable by introducing an
envVariablessection in the CR and allowing users to set
MALLOC_ARENA_MAX. Default: (node height) * (CPUs per unit)
auditlog_levelglobal variable. The following variables are currently supported:
RELATED_IMAGE_NODEis specified, the Operator will pull and use this image to launch all MemSQL node pods as well as the sidecar container.
ProcessStateproperty returned from
glibc tunablesin CR
8 * (node height) * (CPUs per unit)
--fs-group-idflag, which allows you to inject an additional group id into the container running MemSQL. This is used to ensure that the process inside the container has the correct permissions to read/write to the
serviceSpec. The fields and usage of this are described in the Kubernetes deployment guide.
serviceObjectMetaOverridesused in the MemSQLCluster spec are now deprecated. Use
globalVariables. The supported variables are:
snapshot_trigger_size. For more information, see the Kubernetes deployment guide.
adminHashedPasswordcan now can be specified through secrets. To do this, use the alternative attribute