This message was deleted.

Most of the variables can’t be updated after boot at the moment. Some like

OPAL_DATA_CONFIG_SOURCES

can be configured to point to another server to get a dynamic value. We do have plans for more dynamic and easier configuration for OPAL-v2, which is in design stages now. CC: @Shaul Kremer , @Asaf Cohen Feedback here would be welcome, also there is room to volunteer to do dev/design work as part of OPAL v2

I think variables like

DATA_CONFIG_SOURCES

and

OPAL_DATA_TOPICS

should be configurable on the fly if possible. Fetchers I see not being configurable without restarting the pod. Or a new image. If those values were configurable I’d move them into a ConfigMap in k8s. Then it’ll be easier to load/modify them and have k8s reload the env vars.