How to use Secret resources to pass credentials as environment variables into the properties file

You can pass credentials like username or password as environment variables via a Secret resource in Kubernetes. The docker images for previous versions of Scalar products use the dockerize command for templating properties files. The docker images for the latest versions of Scalar products get values directly from environment variables.

Note: You cannot use the following environment variable names in your custom values file since these are used in the Scalar Helm Chart internal.

HELM_SCALAR_DB_CONTACT_POINTS
HELM_SCALAR_DB_CONTACT_PORT
HELM_SCALAR_DB_USERNAME
HELM_SCALAR_DB_PASSWORD
HELM_SCALAR_DB_STORAGE
HELM_SCALAR_DL_LEDGER_PROOF_ENABLED
HELM_SCALAR_DL_LEDGER_AUDITOR_ENABLED
HELM_SCALAR_DL_LEDGER_PROOF_PRIVATE_KEY_PATH
HELM_SCALAR_DL_AUDITOR_SERVER_PORT
HELM_SCALAR_DL_AUDITOR_SERVER_PRIVILEGED_PORT
HELM_SCALAR_DL_AUDITOR_SERVER_ADMIN_PORT
HELM_SCALAR_DL_AUDITOR_LEDGER_HOST
HELM_SCALAR_DL_AUDITOR_CERT_HOLDER_ID
HELM_SCALAR_DL_AUDITOR_CERT_VERSION
HELM_SCALAR_DL_AUDITOR_CERT_PATH
HELM_SCALAR_DL_AUDITOR_PRIVATE_KEY_PATH
SCALAR_DB_LOG_LEVEL
SCALAR_DL_LEDGER_LOG_LEVEL
SCALAR_DL_AUDITOR_LOG_LEVEL
SCALAR_DB_CLUSTER_MEMBERSHIP_KUBERNETES_ENDPOINT_NAMESPACE_NAME
SCALAR_DB_CLUSTER_MEMBERSHIP_KUBERNETES_ENDPOINT_NAME

1. Set environment variable name to the properties configuration in the custom values file. See the following examples based on the product you're using.

ScalarDB Cluster

scalardbCluster:
  scalardbClusterNodeProperties: |
    ...
    scalar.db.username=${env:SCALAR_DB_USERNAME}
    scalar.db.password=${env:SCALAR_DB_PASSWORD}
    ...

ScalarDB Analytics with PostgreSQL

scalardbAnalyticsPostgreSQL:
  databaseProperties: |
    ...
    scalar.db.username=${env:SCALAR_DB_USERNAME}
    scalar.db.password=${env:SCALAR_DB_PASSWORD}
    ...

ScalarDB Server (Deprecated)

ScalarDB Server 3.8 or later (Apache Commons Text syntax)

scalardb:
  databaseProperties: |
    ...
    scalar.db.username=${env:SCALAR_DB_USERNAME}
    scalar.db.password=${env:SCALAR_DB_PASSWORD}
    ...

ScalarDB Server 3.7 or earlier (Go template syntax)

scalardb:
  databaseProperties: |
    ...
    scalar.db.username={{ default .Env.SCALAR_DB_USERNAME "" }}
    scalar.db.password={{ default .Env.SCALAR_DB_PASSWORD "" }}
    ...

ScalarDL Ledger

ScalarDL Ledger 3.8 or later (Apache Commons Text syntax)

ledger:
  ledgerProperties: |
    ...
    scalar.db.username=${env:SCALAR_DB_USERNAME}
    scalar.db.password=${env:SCALAR_DB_PASSWORD}
    ...

ScalarDL Ledger 3.7 or earlier (Go template syntax)

ledger:
  ledgerProperties: |
    ...
    scalar.db.username={{ default .Env.SCALAR_DB_USERNAME "" }}
    scalar.db.password={{ default .Env.SCALAR_DB_PASSWORD "" }}
    ...

ScalarDL Auditor

ScalarDL Auditor 3.8 or later (Apache Commons Text syntax)

auditor:
  auditorProperties: |
    ...
    scalar.db.username=${env:SCALAR_DB_USERNAME}
    scalar.db.password=${env:SCALAR_DB_PASSWORD}
    ...

ScalarDL Auditor 3.7 or earlier (Go template syntax)

auditor:
  auditorProperties: |
    ...
    scalar.db.username={{ default .Env.SCALAR_DB_USERNAME "" }}
    scalar.db.password={{ default .Env.SCALAR_DB_PASSWORD "" }}
    ...

ScalarDL Schema Loader

ScalarDL Schema Loader 3.8 or later (Apache Commons Text syntax)

schemaLoading:
  databaseProperties: |
    ...
    scalar.db.username=${env:SCALAR_DB_USERNAME}
    scalar.db.password=${env:SCALAR_DB_PASSWORD}
    ...

ScalarDL Schema Loader 3.7 or earlier (Go template syntax)

schemaLoading:
  databaseProperties: |
    ...
    scalar.db.username={{ default .Env.SCALAR_DB_USERNAME "" }}
    scalar.db.password={{ default .Env.SCALAR_DB_PASSWORD "" }}
    ...

1. Create a Secret resource that includes credentials.
   You need to specify the environment variable name as keys of the Secret.

   • Example

     kubectl create secret generic scalardb-credentials-secret \
       --from-literal=SCALAR_DB_USERNAME=postgres \
       --from-literal=SCALAR_DB_PASSWORD=postgres

2. Set the Secret name to the following keys in the custom values file. See the following examples based on the product you're using.

ScalarDB Cluster

Key: scalardbCluster.secretName

scalardbCluster:
  secretName: "scalardb-cluster-credentials-secret"

ScalarDB Analytics with PostgreSQL

Key: scalardbAnalyticsPostgreSQL.secretName

scalardbAnalyticsPostgreSQL:
  secretName: "scalardb-analytics-postgresql-credentials-secret"

ScalarDB Server (Deprecated)

Key: scalardb.secretName

scalardb:
  secretName: "scalardb-credentials-secret"

ScalarDL Ledger

Key: ledger.secretName

ledger:
  secretName: "ledger-credentials-secret"

ScalarDL Auditor

Key: auditor.secretName

auditor:
  secretName: "auditor-credentials-secret"

ScalarDL Schema Loader

Key: schemaLoading.secretName

schemaLoading:
  secretName: "schema-loader-ledger-credentials-secret"

1. Deploy Scalar products with the above custom values file.

   After deploying Scalar products, the Go template strings (environment variables) are replaced by the values of the Secret.

   • Example

     • Custom values file

       scalardb:
         databaseProperties: |
           scalar.db.contact_points=jdbc:postgresql://postgresql-scalardb.default.svc.cluster.local:5432/postgres
           scalar.db.username={{ default .Env.SCALAR_DB_USERNAME "" }}
           scalar.db.password={{ default .Env.SCALAR_DB_PASSWORD "" }}
           scalar.db.storage=jdbc

     • Properties file in containers

       scalar.db.contact_points=jdbc:postgresql://postgresql-scalardb.default.svc.cluster.local:5432/postgres
       scalar.db.username=postgres
       scalar.db.password=postgres
       scalar.db.storage=jdbc

   If you use Apache Commons Text syntax, Scalar products get values directly from environment variables.