Latest Chart Version: View on Artifact Hub
- OSS
- Enterprise
Prerequisites
- Kubernetes cluster (v1.19+)
kubectlconfigured- Helm 3.2.0+ installed
- Persistent Volume provisioner (required for SQLite; optional for Postgres-only)
If you use PostgreSQL for Bifrost storage, ensure the database is UTF8 encoded. See PostgreSQL UTF8 Requirement.
Step 1 - Add the Helm Repository
Step 2 - Install
The Helm chart ships ready-made values files under
helm-charts/bifrost/values-examples/.
For example: sqlite-only.yaml, production-ha.yaml, external-postgres.yaml, and secrets-from-k8s.yaml.
See the full list here: https://github.com/maximhq/bifrost/tree/main/helm-charts/bifrost/values-examples- Minimal (SQLite)
- With a Provider Key
- Production (PostgreSQL + HA)
Fastest way to get running. Bifrost deploys as a StatefulSet with a 10Gi PVC for SQLite.
image.tag is required - the chart will not start without it. Check Docker Hub for available versions.Step 3 - Verify
Step 4 - Configure Providers & Plugins
Operations
Upgrade
Rollback
Scale
Uninstall
Monitoring
Prometheus Metrics
Bifrost exposes Prometheus metrics at/metrics (/<prefix>/metrics through an ingress when bifrost.server.basePath is set).
If you run the Prometheus Operator (for example through kube-prometheus-stack), enable the bundled ServiceMonitor for automatic scraping. The monitoring.coreos.com/v1 CRDs must be installed when the manifest is applied; rendering does not need them, so helm template, Argo CD and Flux work offline.
ServiceMonitor scrapes the service’s http port directly, so its path stays /metrics even when bifrost.server.basePath is set.
Scraping with auth enabled. When bifrost.authConfig.isEnabled or bifrost.governance.authConfig.isEnabled is on, /metrics requires credentials too. An unauthenticated scrape gets a 401 and the target sits at up=0 without any error. Turn on basicAuth so the scrape sends the admin credentials:
- In the release namespace,
basicAuthinherits the Secret and key names from the activebifrost.governance.authConfig(preferred) orbifrost.authConfig. If you setserviceMonitor.namespaceto another namespace, setserviceMonitor.basicAuth.existingSecret(andusernameKey/passwordKey) to a Secret in that namespace. - Bifrost reads the Secret as environment variables at pod start, so restart the pods after rotating it (
kubectl rollout restart); until then scrapes get401. - For a bearer token instead, set
serviceMonitor.authorization.credentialsto a Secret key reference. It cannot be combined withbasicAuth. - The render fails rather than producing a
ServiceMonitorthat can never scrape: when no Secret can be resolved, when both auth methods are set, whenauthorizationhas nocredentials, or whenbifrost.plugins.telemetry.config.metrics_enabledisfalse(/metricsthen returns404).
Health Checks
Check pod health:Metrics Endpoints
Configuration Guides
Values Reference
All parameters, secret references, advanced config, example patterns
Client Configuration
Pool size, logging, CORS, header filtering, compat shims, MCP settings
Provider Setup
OpenAI, Anthropic, Azure, Bedrock, Vertex, Groq, self-hosted
Storage
SQLite, PostgreSQL, ClickHouse logs, object storage for logs, vector stores
Plugins
Telemetry, logging, semantic cache, OTel, Datadog, governance
Governance
Budgets, rate limits, virtual keys, routing rules
Alerting
Alert channels, CEL rules, history retention, webhook network controls
Cluster Mode
Multi-replica HA, gossip, peer discovery
Troubleshooting
Pod startup, database, ingress, PVC, secrets, performance
Secret Management
AWS Secrets Manager, GCP Secret Manager, HashiCorp Vault, Azure Key Vault - vault references in provider keys and credentials
Resources
Next Steps
- Configure provider keys
- Enable plugins
- Set up observability
- Configure governance

