Deploys a self-hosted Metabase instance for building dashboards and running SQL queries. Once installed, you connect Metabase to your data sources (Postgres, MySQL, or any JDBC-compatible database) through its admin UI.
Installs a single Helm release in the metabase namespace. For Metabase's own application data (saved questions, dashboards, user accounts), you choose between an embedded H2 database (no setup, fine for trying things out) or an external Postgres backend (supports replicas and proper backups).
Enable "Expose Dashboard" to publish the Metabase UI at <installation-name>.<environment-domain> with auto-provisioned TLS.
This blueprint accepts 10 configurable inputs to customize the installation for your environment.
exposeDashboardbooleanPublish the Metabase UI at a public HTTPS URL.
encryptionKeystringMetabase encryption key for data at rest. Auto-generated if not provided.
databaseTypestringH2 is an embedded database that works out of the box with no setup. Postgres is better for production since it supports multiple replicas and proper backups.
databaseHoststringPostgres host address.
databasePortnumberPostgres port.
databaseNamestringPostgres database name.
databaseUsernamestringPostgres username.
databasePasswordstringPostgres password. Auto-generated if not provided.
storageSizeGinumberPersistent storage size in GiB for the H2 database.
sizestringHow much CPU and memory to allocate. Small works for a few users, Standard for most teams, Large for heavy concurrent usage.
This blueprint exposes 2 outputs that other services can reference.
dashboardUrlstringPublic HTTPS URL for the Metabase dashboard.
internalUrlstringCluster-internal URL for the Metabase service.