Configuration

The values below configure a Deckhouse Code Helm release beyond the minimal install from Quick start. Every value name here is the same as in the chart’s values.yaml; Advanced configuration lists every value the chart accepts.

Hosts and ingress

global.hosts.domain sets the base domain for the instance. global.ingress.class selects the ingress controller that serves it. The chart creates an Ingress object for the web interface at this domain, and one more for each optional component that is enabled, such as the container registry or Pages.

global:
  hosts:
    domain: code.example.com
  ingress:
    class: <INGRESS_CLASS_NAME>

TLS

global.ingress.tls.secretName names the Kubernetes Secret with the certificate and private key for global.hosts.domain. Every Ingress object the chart creates references this Secret.

global:
  ingress:
    tls:
      secretName: <TLS_SECRET_NAME>

The Secret must exist in the release’s namespace before you run helm upgrade; the chart does not create or renew it.

PostgreSQL

global.psql.host and global.psql.port address the external PostgreSQL server. global.psql.database and global.psql.username select the database and the role Deckhouse Code connects as. global.psql.password.secretName and global.psql.password.key point to the Secret with the password.

global:
  psql:
    host: <POSTGRESQL_HOST>
    port: 5432
    database: <POSTGRESQL_DATABASE>
    username: <POSTGRESQL_USERNAME>
    password:
      secretName: <POSTGRESQL_PASSWORD_SECRET>
      key: password

Every component that reads or writes application data connects to this server; the chart does not deploy PostgreSQL.

Redis

global.redis.host and global.redis.port address the external Redis server. global.redis.password.secretName and global.redis.password.key point to the Secret with the password, when the server requires one.

global:
  redis:
    host: <REDIS_HOST>
    port: 6379
    password:
      secretName: <REDIS_PASSWORD_SECRET>
      key: password

Redis holds background job queues, caches and sessions; the chart does not deploy Redis.

Object storage

global.appConfig.object_store.enabled turns on S3-compatible object storage for CI/CD artifacts, uploads and backup archives. global.appConfig.object_store.connection.secretName names the Secret with the endpoint, region and access keys.

global:
  appConfig:
    object_store:
      enabled: true
      connection:
        secretName: <OBJECT_STORE_CONNECTION_SECRET>

Git storage (Gitaly persistence)

gitaly.persistence.size sets the size of the persistent volume claim each Gitaly pod mounts for Git repository storage. gitaly.persistence.storageClass selects the StorageClass it is provisioned from.

gitaly:
  persistence:
    size: <VALUE>
    storageClass: <STORAGE_CLASS_NAME>

Container registry

registry.enabled turns on the container registry component. registry.storage.bucket names the object storage bucket it stores image layers in, using the connection Secret from global.appConfig.object_store.connection.secretName.

registry:
  enabled: true
  storage:
    bucket: <REGISTRY_BUCKET_NAME>

Pages

pages.enabled turns on the Pages component. pages.storage.bucket names the object storage bucket its published sites are stored in.

pages:
  enabled: false
  storage:
    bucket: <PAGES_BUCKET_NAME>

SMTP

global.smtp.enabled turns on outgoing notification email. global.smtp.address and global.smtp.port address the SMTP server. global.smtp.credentialsSecret names the Secret with the user name and password.

global:
  smtp:
    enabled: true
    address: <SMTP_HOST>
    port: 587
    credentialsSecret: <SMTP_CREDENTIALS_SECRET>