for fileserver the persistent volume need to be provisioned by a storageclass. Ususally I always set it to standard
becase itβs commonly used in public cloud providers
so we also improved the chart, superhappy π
thanks a lot π that was quick π
using the --set
you adviced above right?
thanks a lot! So as long as we have the storageclass in our kubernetes cluster configured correctly, the new helm chart should work out of the box?
many thanks π I am going to play with ClearML a little bit and re-read carefully the thread to learn something from what you made me do today!
perfect, let me try π (thanks a lot for all the help!)
i will release a new chart version with no need to set a default storage class like I asked you to do today
now Iβm leaving for today but let me know if it works. Have an nice day!
I absolutely need to improve the persistence part of this chart π
just to understand well the problems you helped me fix:
for elastic search it looked like I wasn't running the cluster with enough memory
but what happened to the FileServer? and how can I prevent it happening in a potential "production" deployment?
but Iβm going to patch this soon so it will take the default storageclass automatically
this is the PR https://github.com/allegroai/clearml-helm-charts/pull/66 ; when CI will be passed Iβm going to release the new chart
with this one you donβt need anymore to set the value I suggested before