Sync Variables with the Operator

{question}

Why Are Sync Variables Set in the CR Manifest Not Honored in My SingleStore Operator Cluster?

{question}

{answer}

Issue:
You're setting sync variables through the Custom Resource (CR) manifest in your SingleStore Operator-managed cluster, but they don’t appear to take effect. Why is this happening?

Explanation:
Sync variables are a special class of engine variables intended to propagate across nodes in the cluster. You can read more about them in SingleStore's documentation.

These variables are designed to be set by connecting to the database and issuing a SET GLOBAL command. As such, the SingleStore Operator does not apply sync variables automatically when specified in the CR manifest after the cluster has already been deployed.

Recommended Approach:

• For initial deployments:
  You can include sync variables in the globalVariables section of your CR manifest. The Operator will apply them when the cluster nodes are first launched.

• For existing/running clusters:
  Sync variables must be set manually by connecting to the database and running the appropriate SET GLOBAL command. Changes through the CR manifest will not be honored once the cluster is already running.

Summary:
Sync variables must be applied from within the database after deployment. The CR manifests globalVariables The section only supports sync variable configuration during initial cluster setup.

{answer}