CONFIG_PATH to the file’s path; mount your file there.
Every file follows the rules of
routr.yaml: placeholders, secret:// references, the server keys on every gRPC service and the client keys for every peer a component dials. Every file also takes logLevel (debug, info, warn or error, default info) and telemetry at its root.
Most files keep their Routr 2 shape, so a Routr 2 file still loads. Every file requires apiVersion: v2beta1, v2 or v3; the examples use v3. They differ from routr.yaml in one way: except for connect.yaml, rtprelay.yaml’s spec and the Data API’s spec.data, they ignore keys they don’t know, as Routr 2 did.
edgeport.yaml
Routr 2’sedgeport.yaml, unchanged. The spec keys are those of spec.edgeport, with these differences:
edgeport.yaml
CONFIG_PATH and nothing else from its environment. Routr 2’s EdgePort variables are keys of this file; see Environment variables for the map.
dispatcher.yaml
Routr 2’sdispatcher.yaml, plus authentication.
dispatcher.yaml
location.yaml
Routr 2’slocation.yaml, plus authentication.
location.yaml
connect.yaml
New in Routr 3: Routr 2’s Connect read these settings from its environment. The names are the same, in camelCase underspec. Unknown keys are rejected.
A DNS name in
trustedRegistryAddresses is resolved every 10 seconds. If it stops resolving, Connect keeps its last addresses for 30 seconds and then trusts nothing. With a Registry, set this key, or the Trunks’ REGISTER requests are refused.
connect.yaml
data.yaml
The Data API reads a file in the shape ofroutr.yaml and uses only logLevel, telemetry and spec.data. Other sections are ignored, so RoutrOne’s file works too. The keys are those of spec.data.
data.yaml
fonoster/routr-pgdata-migrations image, built from ops/pgdata-migrations with Routr 2’s migrations unchanged, which the Helm chart runs at its appVersion.
requester.yaml
New in Routr 3: Routr 2’s Requester read no file. WithoutCONFIG_PATH it takes the defaults, which bind every address with no authentication, and so it refuses to start.
requester.yaml
registry.yaml
Routr 2’sregistry.yaml, plus authentication.
registry.yaml
rtprelay.yaml
Routr 2’srtprelay.yaml, which now also holds what Routr 2 read from RTPENGINE_HOST, RTPENGINE_PORT and RTPENGINE_TIMEOUT. The file is required. spec rejects unknown keys.
rtprelay.yaml
Related
routr.yaml
Every key, and how values and secrets resolve.
Helm values
The chart writes these files from its values.