Repository navigation
[feature] Provision a transcode node's key from config, without admin UI #4594
jasonpanosso
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Problem
I deploy Silo via Kubernetes, with secrets generated by a secrets manager. I have the ability to generate keys for the transcode nodes on demand, but there's no way for me to configure Silo to utilize these keys, as the only way to configure a new transcode node is via the UI/API. Transcode nodes accept
SILO_NODE_KEY. It would be convenient if the API server also accepted some env var, or file path to read transcode node configuration (name/key/etc). After #4499, I have everything about the transcode nodes setup via yaml, except its entry & its key.Who it affects
Users who deploy silo with separate API & transcode nodes, setup declaratively via compose files/kubernetes/ansible/etc who do not want to go through the manual steps of generating the node keys in UI. It mainly affects users who deploy multiple transcode nodes, as each node will require manual steps to set up.
Current workaround
Deploy a transcode node with no key, create its entry & issue the key in the web UI, copy the key into the secrets manager, configure the nodes
SILO_NODE_KEYto be pulled from the secret manager, then restart the node.Proposed behavior
Allow API servers to read transcode node definitions (name/key) from an env var or mounted file.
Alternatives considered
some init job that scripts the admin API is an alternative, but IME random shell scripts like this are flaky and prone to failing over time
AI harness
none
AI tool(s)
none
AI model(s)
n/a
AI involvement
No AI used
Independent or adversarial review
n/a
Confirmations
All reactions