Skip to main content
This page shows how to override the default engine and metadata image tags. By default, the chart pulls the engine through Firebolt’s Scarf gateway at oci.firebolt.io/firebolt-db/engine and metadata directly from ghcr.io/firebolt-db/metadata, using the appVersion in Chart.yaml. To bypass Scarf for engine pulls, set:
Setting telemetry.enabled: false has the same effect on the default engine repository — it switches pulls to ghcr.io/firebolt-db/engine (an explicitly configured repository is preserved) and additionally sets DO_NOT_TRACK=1 on every engine container, disabling the engines’ once-daily anonymous usage event.

​
Track ‘dev’ images

To follow current-of-mainline builds, you can use the dev tag.
The dev tag is mutable. Two installs minutes apart can pull different content. Pin the tag to a specific version for reproducible installs.

​
Use a specific build

You can override the tag per component, but you must keep the version used for the Engine and used for the Metadata Service in lockstep. You can choose the smaller release- versions or use the debug- prefix which contains debug symbols.

​
Lockstep

Engine and metadata ship from the same build pipeline and are not version-tolerant of each other. The chart does not enforce lockstep. Mismatched tags surface as a metadata-RPC failure at engine startup.