Also k8s distribution and version you are using can be useful
can you pls put the entire helm list -A output command?
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
with that in place k8s should be able to provisione pvc
Client Version: v1.25.3
Kustomize Version: v4.5.7
Server Version: v1.25.3
so the missing volume, do you have a recommendation how do i solve this?
i want the storage to be on NFS eventually, the NFS is mounted to a local path on all the nodes (/data/nfs-ssd)
you need to investigate why it’s still in Pending state
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
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
currently http://kubernetes.io/no-provisioner
same , when i'm installing directly: sudo helm install clearmlai-1 allegroai-clearml/clearml -n clearml
seems like i didn't define a persistant volume
i set it as default the results are the same
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/
can you also show output of kubectl get po of the namespace where you installaed clearml?
hi i tried a new installation using the files downloaded just perform : helm install clearml . -n clearml
without changing anything.
the problem persist.



