Configure OpsKnight Helm values

The chart validates values against values.schema.json. Render and schema validation reduce configuration mistakes but do not prove the deployment is secure or operationally sized.

Core value groups

• runtime.mode: integrated or split; PgBouncer requires split.
• image: repository, tag/digest, pull policy, and pull Secrets. Digest takes precedence.
• config: public origins and common runtime settings.
• secrets: use an existing production Secret and explicit key mapping.
• migrations.job.enabled: creates the pre-install/pre-upgrade migration hook.
• postgresql: bundled database, storage, resources, credentials, and CA mounting.
• database: application endpoint and aggregate connection ceiling.
• pgbouncer: Web-only transaction pooling in split mode.
• web, scheduler, and worker/status groups: replicas, pools, resources, concurrency, disruption, and termination.
• service and ingress: public routing.
• probe groups: startup, liveness, and readiness behavior.
• networkPolicy: ingress selectors and database/provider egress.
• metrics.serviceMonitor: Prometheus Operator discovery and scrape-token Secret.

Production rules

Keep production values outside the chart directory, pin the chart source revision and image digest, use a managed Secret, and review the complete rendered output. Never store cleartext production secrets in Helm values because release state can retain them.

Validate values

helm lint deploy/kubernetes/helm/opsknight -f values.production.yaml
helm template opsknight deploy/kubernetes/helm/opsknight \
  --namespace opsknight -f values.production.yaml > rendered.yaml
kubectl apply --dry-run=server -f rendered.yaml

Inspect images, Secret references, migration ownership, database paths, Services, ingress, NetworkPolicy, resources, probes, PDBs, and replica counts before installation.

Related guides

• Install with Helm
• Integrated values
• Split values