The Helm Chart deploys Deckhouse Code directly to a Kubernetes cluster, without the Deckhouse Kubernetes Platform module. The cluster and the services below must already exist before you install the chart.
Kubernetes cluster
The cluster runs Kubernetes version <VALUE> or later.
Helm
The chart installs with Helm 3.
Ingress controller
An ingress controller is already running in the cluster. The chart creates Ingress objects for the web interface and for the optional container registry and Pages components; each one uses the ingress class named in global.ingress.class.
Default StorageClass
A default StorageClass, or a StorageClass named explicitly in gitaly.persistence.storageClass, so the cluster can provision the persistent volume claim each Gitaly pod uses for Git repository storage.
External PostgreSQL
An external PostgreSQL server, addressed by global.psql.host, that stores Deckhouse Code’s application data. The chart does not deploy a database.
External Redis
An external Redis server, addressed by global.redis.host, used for background job queues, caching and session storage. The chart does not deploy Redis.
Object storage
An S3-compatible object storage bucket, configured through global.appConfig.object_store, that stores CI/CD artifacts, uploads and backup archives. The chart does not deploy object storage.
DNS name and TLS certificate
A DNS name for the instance, set in global.hosts.domain, that resolves to the ingress controller’s address. A TLS certificate for that name, supplied as a Kubernetes Secret named in global.ingress.tls.secretName, whether issued manually or by a certificate manager already running in the cluster.