Skip to main content
The routr/routr-connect chart deploys EdgePort, Message Dispatcher, Connect processor, Location Service, API Server (pgdata), Registry, Requester, and optionally RTPRelay. It can also deploy PostgreSQL and Redis from the Bitnami charts. Image tags default to the chart’s app version.

Install

These commands add the chart repository and install a release named routr in the routr namespace.
This command overrides values from a file.

Common value groups

Each service section has the same groups. They are listed once here and referenced by section below. Per-service defaults:

global

edgeport

The TCP Service is created only when TCP, TLS, WS, or WSS is enabled. The UDP Service is created only when UDP is enabled.

dispatcher

location

apiserver

connect

The chart sets LOCATION_ADDR and API_ADDR for you.

registry

requester

rtprelay

Enabling RTPRelay does not add it to the Dispatcher. Add an entry to dispatcher.middlewares, for example {ref: rtprelay, serviceName: routr-rtprelay, postProcessor: true}.

postgresql

Values from the Bitnami PostgreSQL chart, chart version 16.2.2.

redis

Values from the Bitnami Redis chart, chart version 20.3.0.

Notes

  • global.otlExporter sets OTEL_EXPORTER_JAEGER_ENDPOINT, but the Routr services read the standard OTEL_EXPORTER_OTLP_ENDPOINT. See Environment variables.
  • The chart does not set TRUSTED_EDGEPORT_ADDRESSES on the Connect processor. With more than one EdgePort replica, requests forwarded between EdgePorts go through routing and access checks again. See Connect processor.
  • The chart has no values for Connect settings such as ENFORCE_E164 or the Connect Token verifier.