Keep the pod configuration defined after Sisense update

In our use case, we need to modify the configuration of certain pods such as exporting, external-plugins, and exporter-xlsx using the kubectl edit command. We have noticed that with each Sisense version upgrade, these changes are lost — meaning the configuration values revert to their default, pre-modification state.
Would it be possible to retain these modifications after a Sisense version upgrade?

Kevin S

Posted 1 year ago·Last reply 1 year ago

2 comments

DRay

·1 year ago

Hello kseri,

Thank you for reaching out. There is a way to retain those settings. Can you check this doc and let us know if it provides a solution for you?

https://docs.sisense.com/main/SisenseLinux/installing-sisense-using-provisioner-and-helm.htm

Kevin S

OP1 year ago

Hello DRay ,

Thank you for the documentation ! I will check this documentation and I will tell you if fit my needs.