it can help debugging

In fact it's the same we are applying to helm charts for k8s

You are not cheating 😂

I'm going to ask an update to docs

Can you pls share all 3 health checks ?

Just to be sure we are in sync 😁

checking more

today it's pretty busy for me but I can try to help if needed, pls put any question here if you have and I will try to answer when possible

it would be great to get logs from apiserver and fileserver pods when deleting a file from ui so we can see what is going on. I’m saying this because, at first glance, I don’t see anyissue in your config

ok, ty very much for your feedback 😄

O k, I’d like to test it more with you; credentials exposed in chart values are system ones and it’s better to not change them; let’s forget about them for now. If you create a new accesskey/secretkey pair in ui, you should use these ones in your agents and they shuld not get overwritten in any way; can you confirm it works without touching credentials section?

ty

regardless of this I probably need to add some more detailed explanations on credentials configs

and then use them in agents if they are external

y ou can siply generate in UI the keys

Exactly, these are system accounts

if they are in kubernetes you can simply use k8s glue

Hey ApprehensiveSeahorse83 , I didn’t forget about you, it’s just a busy time for me; will answer during the day after a couple of more tests on my testing env.

ty for your patience

In this case I suggest to give a try to k8s-glue that is there by default in latest chart version

but Agents are on same k8s?

Interesting use case, maybe we can create multiple k8s agents for different queues

I’m going to investigate this specific use case and will get back to you

Hi ApprehensiveSeahorse83 , today we released clearml-agent chart that just installs glue agent. My suggestion is to disable k8s glue and any other agent from the clearml chart and install more than one clearml-agent chart in different namespaces. In this way you will be able to have k8s glue for every queue (cpu and gpu).

in some second it should became green

Maybe it can be enough to set annotations in ingress section

other wise yes, if this is not an option, you can also mount what is already existing so pls open an issue in new repo helm chart and we can find a solution

Hi BurlySeagull48 , I’m interested in your use case and I think we can find a solution. NFS mounts have the same path in every node?

ok this is weird, in apiserver we should see call for deletion request. I need to consult with some people because I don’t think this is infra config related.

Or do you want to dinamically mount directly an nfs endpoint? (I understood you need this one)