---
# The secret name must match your Helm release name followed by "-secrets".
# For example, if your release name is "kasm", the secret name must be "kasm-secrets".
# This must be set before running: helm install {RELEASE_NAME} ...
apiVersion: v1
kind: Secret
metadata:
  name: "{RELEASE_NAME}-secrets"  # <-- REPLACE {RELEASE_NAME} with your Helm release name
type: Opaque
data:
  manager-token: "base64 encoded kasm manager token"
  service-token: "base64 encoded kasm service token"
  db-password: "base64 encoded kasm db password"
  # Optional values - is very useful to have to ensure consistency across deployments
  # as the new helm chart will create a secret called "release-name-secrets" and will
  # automatically generate these values if they don't exist in this secret. This could
  # cause confusion if users are unaware that the passwords stored here are not valid.
  admin-password: "base64 encoded kasm admin password"
  user-password: "base64 encoded kasm user password"