🎄 Happy Holidays! 🥳
Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.
Happy Holidays!
Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.
Changing size of a solace kubernetes deployment
Hi all,
I'm relatively new to Solace on Kubernetes.
We currently have a standalone deployment running in an Azure kubernetes cluster. Its the default prod100 size and uses persisted volumes. Its deployed via helm.
Recently we hit the size limit of 100 as the number of users connecting increased.
I figured out that we need to redeploy via helm with a size change to prod1k.
Before i do this in production, i need to be sure i won't lose any data.
If i simply update my helm chart with prod1k size and run an helm upgrade/install, will it rebuild the existing pubsubplus pod as a prod1k size and keep the existing data on the persisted volume? or do i need to do something else like attaching to a pre-existing persistent volume?
Thanks in advance,
Regards,
Les
