oh now I understand

same , when i'm installing directly: sudo helm install clearmlai-1 allegroai-clearml/clearml -n clearml

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

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?

seems like i didn't define a persistant volume

you need a dynamic capable provisioner

i'm running on bare metal cluster if that matter

that sc is not set as default

i see, checking

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

with that in place k8s should be able to provisione pvc

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

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/

elastic is not being scheduled

i set it as default the results are the same

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

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

this is the problem the elastic pod shows:
Events:
Type Reason Age From Message

Warning FailedScheduling 65s (x2 over 67s) default-scheduler 0/6 nodes are available: 6 pod has unbound immediate PersistentVolumeClaims. preemption: 0/6 nodes are available: 6 Preemption is not helpful for scheduling.

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

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

clearml-4.3.0

is there a mount i need to add?