How can I add custom environment variables to noobaa-core deployment through noobaa operator ?

[NoOverflow]

Hi,

I would like to modify NooBaa's default behaviour without having to build a new image with a modified config.js. (Would like to enable config.WORM_ENABLED to allow object lock).

Reading the code I found out that this can be done using environment variables prefixed with CONFIG_JS_ (https://github.com/noobaa/noobaa-core/blob/4847584ca6b10aeea6f596b30edaabf91a3ce7ae/config.js#L1015).

Unfortunately the NooBaa CR doesn't seem flexible enough to allow a user to specify custom environment variables (https://github.com/noobaa/noobaa-operator/blob/master/deploy/internal/statefulset-core.yaml)

Am I correct to assume that for now, building a new image is the only way for me to modify this ? Or am I missing something ?

Thanks

[nimrod-becker]

@dannyzaken @jackyalbo

[NoOverflow]

Any idea ? If not I'll see if I can open a PR to allow custom env vars in the operator CRDs

[NoOverflow]

Started experimenting over at https://github.com/NoOverflow/noobaa-operator/commits/master/. Will open a PR once I've got something that works.