Skip to main content
The release bundle ships three values files, which are your starting point: values/jedify-infra.yaml for the platform chart, and values/jedify-be.yaml plus values/jedify-be-workers.yaml for the application chart’s two releases. Each chart’s own values.yaml carries working defaults for everything those files don’t set. Where the bundle’s file sets a different value from the chart, the Default column shows the bundle’s value and names the chart’s.
Lists replace; maps merge. A list in your values replaces the chart’s whole list instead of adding to it. Set gateway.healthChecks to add one entry and you’ve removed the others, which shows up as a service answering 503 while its pods are ready. When you override a list, restate every entry you want to keep.

jedify-infra

Where pods run

Google Cloud

Application secrets

Egress

Model proxy

Realtime

Web app

Gateway

Certificates

cert-manager needs Gateway API support turned on in its controller configuration. It isn’t a feature gate: passing one changes nothing, and challenges stay pending with gateway api is not enabled.
You create the issuer and the Certificate yourself; the Certificate writes the jedify-tls Secret.

Zitadel

Reloader

Reloader restarts a workload when a Secret or ConfigMap it reads changes. It acts only in the namespaces listed and only on workloads that opt in.

jedify-be

Routing

Identity and secrets

Realtime

Components

Workers release

These keys are in values/jedify-be-workers.yaml, which the workers release adds on top of values/jedify-be.yaml.

Application environment

externalSecret.plainEnv in values/jedify-be.yaml. Plain environment variables override keys of the same name in your application configuration secret, so don’t set a key here that belongs there, such as the Zitadel settings.