Camunda Community Hub
Persistent volume claim #154
-
|
Hi All, I am new to camunda8, I had installed Camunda8 self managed in AKS using helm chart. I just need to ask that while installation there is a default elasticsearch pvc created which is of 64Gi. so is there any way to autoscale this pvc later depending on the usage. Thank you for any information or help. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hey @purohitamit, this GitHub Discussions is for questions related to the Camunda Community Hub and the community-led projects here -- in the future, the Camunda forum is your best bet for usage questions. To try and answer your question -- if you used the Helm chart at helm.camunda.io, it should be sufficient for 80% of use cases, but you can adjust the default size to fit your environment. I encourage you to read a bit more about how scaling works on that same docs page. It's a little bit different than adding more Kubernetes pods, as that doesn't always add more throughput. That said, you can also look into Kubernetes’ own autoscaler -- here’s the one for AKS. |
Beta Was this translation helpful? Give feedback.
-
|
Hi xomiamoore for the info. I will go through the docs again. |
Beta Was this translation helpful? Give feedback.
Hey @purohitamit, this GitHub Discussions is for questions related to the Camunda Community Hub and the community-led projects here -- in the future, the Camunda forum is your best bet for usage questions.
To try and answer your question -- if you used the Helm chart at helm.camunda.io, it should be sufficient for 80% of use cases, but you can adjust the default size to fit your environment.
I encourage you to read a bit more about how scaling works on that same docs page. It's a little bit different than adding more Kubernetes pods, as that doesn't always add more throughput. That said, you can also look into Kubernetes’ own autoscaler -- here’s the one for AKS.