britive/bridge-chart repository overview

⁠Britive Bridge — Helm chart

The Helm chart for deploying Britive Bridge in clustered mode on Kubernetes. An orchestrator owns schema migrations, leader election, and reconciliation, and provisions session/proxy worker pods via the in-cluster driver (no static worker Deployments); a Service fronts the ready proxies.

The container image is published separately at britive/bridge⁠.

⁠Install

helm install bridge oci://registry-1.docker.io/britive/bridge-chart \
  --version <x.y.z> -n bridge --create-namespace \
  --set secrets.clusterToken="$(openssl rand -hex 32)" \
  --set secrets.encryptionKeyB64="$(openssl rand -base64 32)" \
  --set secrets.hostKeySeed="$(openssl rand -hex 32)" \
  --set config.auth.britive.tenant=https://<tenant>.britive-app.com \
  --set recordings.mode=hostPath \
  --set orchestrator.replicas=1

This brings up a bundled PostgreSQL and single-node hostPath recording storage for evaluation. For production, set postgres.enabled=false and point datastore.* at managed PostgreSQL, back recordings with a ReadWriteMany StorageClass, and set secrets.brokerAuthToken to auto-retrieve the license. See values.yaml for all options.

⁠Documentation

Full documentation is available @ learn.britive.com⁠.