Secrets Management

Secrets Management

This page describes how to manage custom secrets for SD Elements. For the standard installation, the Helm chart will automatically generate the secrets. See the documentation here Install SD Elements for more information.

Reference Existing Secrets

It is possible to provide custom secrets to override the automatically generated ones. This can be useful in scenarios where you want to manage secrets externally or have specific security requirements. To use custom secrets, you need to define them in your custom values file. Below is an example of how to set custom secrets for sde

sde:
  secretName: sde-secrets
postgresql:
  auth:
    existingSecret: sde-database
    secretKeys:
      adminPasswordKey: postgres-password
      userPasswordKey:  password
rabbitmq:
  auth:
    existingPasswordSecret: sde-broker
  existingPasswordSecret: rabbitmq-password
  existingErlangSecret: rabbitmq-erlang-cookie
minio:
  existingSecret: sde-minio
sc-datastore:
  secretName: sde-datastore-secrets
  secretKey: ADMIN_DATASTORE_PASSWORD
sc-conjure:
  secretName: sde-conjure-secrets
  database:
    secretName: sde-database
  broker:
    secretName: sde-broker
  sde:
    secretName: sde-secrets
Make sure to create the Kubernetes secrets referenced in the configuration above before deploying or upgrading your Helm chart. Below is a list of the required secrets and their keys. The keys should match those specified in the Custom Secrets section of the configuration unless specfically allowed to be overriden (rabbitmq, postgresql, sc-datastore). 
# sde-secrets
S3_ACCESS_KEY
S3_SECRET_KEY
SDE_JWT_SECRET
SDE_SECRET_KEY
SDE_SUPERUSER_PASSWORD

# sc-conjure-secrets
OPENAI_API_KEY
ROBOFLOW_API_KEY
ROBOFLOW_API_URL

# sc-datastore-secrets
ADMIN_DATASTORE_PASSWORD

# sde-broker
rabbitmq-erlang-cookie
rabbitmq-password

# sde-database
password
postgres-password

# sde-minio
rootUser
rootPassword

results matching ""

    No results matching ""