Mount Additional ConfigMaps/Secrets

On this page

Optional ConfigMaps and/or Secrets can be mounted to all pods in the deployed SingleStore cluster. These can be mounted on a per-cluster basis, or, in the case of ConfigMaps, mounted to all SingleStore clusters in the same Kubernetes namespace.

A ConfigMap or Secret will be mounted automatically (which may take a minute or two) when created as per the following instructions.

Mount a ConfigMap to a Cluster

When a ConfigMap is created with the name <cluster-name>-additional-files, the ConfigMap will be mounted automatically on /etc/memsql/extra for all pods in the cluster.

Mount a Secret to a Cluster

When a Secret is created with the name <cluster-name>-additional-secrets, the Secret will be mounted automatically on /etc/memsql/extra-secret for all pods in the cluster.

Mount a ConfigMap to All Clusters in the Same Kubernetes Namespace

When a ConfigMap is created with the name global-additional-files, the ConfigMap will be mounted automatically on /etc/memsql/share for all pods in the cluster within the same Kubernetes namespace.

Last modified: July 5, 2022

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

(Optional) Run the following command to view the associated signature files.
Shell
```
curl undefined
```
Download the signature file from the SingleStore release server.
- Option 1: Click the Download Signature button next to the SingleStore file.
- Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.
- Option 3: Run the following command to download the signature file.
  Shell
```
curl -O undefined
```

After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

Shell

echo -n undefined |
    cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
      --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
      --bundle undefined \
      --new-bundle-format -

Verified OK