this configuration object is stored as a file in /root/.trains ?

a big ty for now

kubectl get ingress -A

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?

s o kubectl -n clearml get ingress

If you have ALB you will just need to add some annotations on ingress rules depending on your setup. btw for now , since you already have everything in place, I suggest to just add values to /etc/hosts and see if it works

it’s alongside health checks tab

usually you can see if you are getting timeouts or wrong http code

in some second it should became green

You are not cheating 😂

ok, ty very much for your feedback 😄

elastic is not being scheduled

about minor releases they are not breaking so it should be linear

I should add some more instruction on Github page

great ty!

but I think this behaviour will hange in future releases

ok so they are executed as expected

There’s an incomplete PR for this None .

Hi Martin 😄 ok got it but now the question: how I can pass this to the train-agent deployed with Helm chart?

there’s anything specific you need?

Hi,
how did you specified it in Helm override file?

btw, judging from screenshots services are ok but pod are not up, especially elastic, redis and mongodb are Pending so it means k8s didn’t scheduled them for some reason you can find describing these pods

not sure if this is ok with your infra

I’m just going to include these credentials in pod template too

at that point we define a queue and the agents will take care of training 😄

clearml-agent is a pretty new chart so I expect some issues. Can you pls open an issue on Github for each problem you found?

it will be easier for me to track fixes

probably you will see it’s not capable of doing it and it should be related k8s config

then I enqueue it and it's created but obv empty

and I will give you feedback here