Set rpc-whitelist-enabled to false by default on first run
Opened this issue · 0 comments
If no transmission daemon config exists (first run or no persistence is set) there is one generated with default setting, where rpc-whitelist-enabled
is set to true
, which leads to lack of ability to get to web UI and change this configuration or add IPs to rpc-whitelist
value.
Need to add init container to set this value to false
and let user change it after
Or even more - map some of the main parameters to questions.yaml
and helm variables.
Keeping all configuration in CM will allow to map them easily but it will mean that config is immutable as CM is RO afaik in k8s and will require to config only via Truenas.
Current WA: after install with config mapped to dataset -> login to truenas and change config manually.