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.
root
user. The default resource pool associated with that user will be used in the backup job.Docker Hub Image | |
memsql/operator:1.2.2-93a97e50 |
sha256:80954740aed76d351b0b1ab1e589ab926f70f11182c89c100cbbebcf1702831f |
rootServiceUser
flag in the CR to control whether to grant SERVICE_USER
to root
.local_file_system_access_restricted
global variable.priorityClassName
via an Operator command-line parameter priority-class-name
. The priorityClassName
will be passed to all StatefulSet’s PodSpec.backup-s3-endpoint
and backup-compatibility-mode
that were inadvertently removed from the Operator 1.2.0 release. Refer to the Backups reference for more information.backup-s3-endpoint
and backup-compatibility-mode
command-line parameters. Refer to the Backups reference for more information.globalVariables
section 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:
redundancy_level
sync_permissions
local_file_system_access_restricted
phase
field to CR status.
Running
indicates that the Operator is happy with the state of the cluster and that there are no more changes to be made.Pending
indicates that the Operator is still working towards a desired state of the cluster.storageGB
field in aggregatorSpec
and/or leafSpec
in CR.memsqlPusherSpec
inside a monitoringSpec
in the CR to allow MemSQL to be configured to push metrics to Kafka.cgroup
-aware and respect container resource boundaries for containerized deployments.
app.kubernetes.io/name=memsql-cluster
to app.kubernetes.io/name=backup
glibc
tunable by introducing an envVariables
section in the CR and allowing users to set MALLOC_ARENA_MAX
. Default: (node height) * (CPUs per unit)auditlog_level
global variable. The following variables are currently supported:
default_partitions_per_leaf
columnstore_segment_rows
columnstore_flush_bytes
columnstore_window_size
transaction_buffer
snapshot_trigger_size
minimal_disk_space
pipelines_max_concurrent
auditlog_level
nodeSelector
, affinity
, anti-affinity
, toleration
, schedulerName
, and nodeName
in PodSpecdefault_partitions_per_leaf
, columnstore_segment_rows
, columnstore_flush_bytes
, columnstore_window_size
, transaction_buffer
, snapshot_trigger_size
, minimal_disk_space
, pipelines_max_concurrent
RELATED_IMAGE_NODE
is specified, the Operator will pull and use this image to launch all MemSQL node pods as well as the sidecar container.ProcessState
property returned from memsqlctl
glibc tunables
in CR
glibc.malloc.arena_max
= 8 * (node height) * (CPUs per unit)
1
.--fs-group-id
flag, 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 /var/lib/memsql
volume.serviceSpec
. The fields and usage of this are described in the Kubernetes deployment guide.loadBalancerSourceRanges
and serviceObjectMetaOverrides
used in the MemSQLCluster spec are now deprecated. Use serviceSpec
moving forward.globalVariables
. The supported variables are: license_visibility
, default_partitions_per_leaf
, columnstore_segment_rows
, columnstore_flush_bytes
, columnstore_window_size
, transaction_buffer
, and snapshot_trigger_size
. For more information, see the Kubernetes deployment guide.license
and adminHashedPassword
can now can be specified through secrets. To do this, use the alternative attribute licenseSecret
or adminHashedPasswordSecret
.