Install dpndncY on Kubernetes with Helm.
Production deployment of the all-in-one image with an optional PostgreSQL backend, ingress, TLS, and OIDC single sign-on.
Add the chart and install
helm
helm repo add dpndncy https://charts.dpndncy.com
helm repo update
helm install dpndncy dpndncy/dpndncy \
--namespace dpndncy --create-namespace \
--set ingress.host=dpndncy.example.com \
--set postgres.enabled=trueCommon values
| Value | Purpose |
|---|---|
image.tag | Pin a released image tag (recommended for production) |
postgres.enabled | Deploy the bundled PostgreSQL, or point externalDatabaseUrl at your own |
ingress.host / ingress.tls | Console hostname + TLS (cert-manager friendly) |
persistence.size | PVC for scan artifacts, signing-key archive, attestation history |
oidc.issuerUrl + client id/secret | SSO via your IdP |
signingKey.existingSecret | BYOK signing key (production) instead of autogen |
resources | Requests/limits — SAST + SCA resolution are CPU-bound during scans |
One image, all engines
The chart runs a single image that bundles the console, every scan engine, the Python SAST analyzers, and the JDK + Maven used for dependency resolution. There is no separate worker image to schedule.
Upgrade
upgrade
helm repo update
helm upgrade dpndncy dpndncy/dpndncy --reuse-values --set image.tag=2026.06Schema migrations run automatically on pod start; rollouts are zero-downtime when postgres.enabled=true and replicaCount > 1.