hint at the expected source and format of the zrok admin tokens

This commit is contained in:
Kenneth Bingham 2023-04-16 16:34:42 -04:00
parent 4a2b69c1f8
commit 1c9d4cc42b
No known key found for this signature in database
GPG Key ID: 31709281860130B6
2 changed files with 4 additions and 2 deletions

View File

@ -12,7 +12,7 @@ Environments that horizontally scale the `zrok` control plane with multiple cont
## Configuring the OpenZiti Controller
> This requires a version of OpenZiti with a `fabric` dependency of `v0.22.52` or newer.
> This requires a version of OpenZiti with a `fabric` dependency of `v0.22.52` or newer, which is satisfed by the `v0.27.6` release of OpenZiti Controller.
Emitting `fabric.usage` events to a file is currently the most reliable mechanism to capture usage events into `zrok`. We're going to configure the OpenZiti controller to append `fabric.usage` events to a file, by adding this stanza to the OpenZiti controller configuration:

View File

@ -50,8 +50,10 @@ Create a controller configuration file in `etc/ctrl.yml`. The controller does no
v: 3
admin:
# generate these admin tokens from a source of randomness, e.g.
# LC_ALL=C tr -dc _A-Z-a-z-0-9 < /dev/urandom | head -c32
secrets:
- f60b55fa-4dec-4c4a-9244-e3b7d6b9bb13
- Q8V0LqnNb5wNX9kE1fgQ0H6VlcvJybB1
endpoint:
host: 0.0.0.0