Keep the pod configuration defined after Sisense update | Product Feedback Forum

kseri · 2025-06-04T14:45:12.577000Z

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?

MoreDiscussions

Keep the pod configuration defined after Sisense update | Product Feedback Forum | Sisense Community