this is basic k8s management that is not strictly related this chart. my suggestion is to have a default storageclass that will be able to provide the right pv/pvc for any deployment you are going to have on the cluster. I suggest to start from here: https://kubernetes.io/docs/concepts/storage/storage-classes/

i see, checking

with that in place k8s should be able to provisione pvc

that sc is not set as default

is there a mount i need to add?

hey, ill appreciate help here. i'm stuck

elastic is not being scheduled

oh now I understand

some suggestions:
start working just with clearml (no agent or serving, these ones will go in after clearml is working) try a fist deploy without any override if it works start adding values to override file (without reporting everything or it will be very difficult to debug, you should not report on override file what is not overridden) do helm upgrade check problems one by one

currently http://kubernetes.io/no-provisioner

Also k8s distribution and version you are using can be useful

so the missing volume, do you have a recommendation how do i solve this?

NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
chart-1669648334 clearml 1 2022-11-28 17:12:14.781754603 +0200 IST deployed clearml-4.3.0 1.7.0

i know what storageclass is.. but i don't think that this is the problem i do have one standard, seems that pv claim do not collecting it

can you pls put the entire helm list -A output command?

i set it as default the results are the same

you need to investigate why it’s still in Pending state

Client Version: v1.25.3
Kustomize Version: v4.5.7
Server Version: v1.25.3

I’m not sure why in your case liveness probe is trying to access a non localhost ip. What is the version of the chart you are trying to install? helm list -A

hi i tried a new installation using the files downloaded just perform : helm install clearml . -n clearml
without changing anything.
the problem persist.

can you also show output of kubectl get po of the namespace where you installaed clearml?

or maybe should i create my own pv?

i want the storage to be on NFS eventually, the NFS is mounted to a local path on all the nodes (/data/nfs-ssd)

this is a clear issue with provisioner not handling the pvc request for any pod having a pvc. It’s not related chart but provisioner you are suing that probably doesn’t support dynamic allocation. what provisioner are you using?