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

I can even specify a tag generated on the fly; superinteresting and I can satisfy my obsession for automation 😄

if they are in kubernetes you can simply use k8s glue

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

hi, pls check first message on this pr conversation; there is a checklist to be completed otherwise CI will not complete

if mounts are already there everywhere you can also mount directly on the nodes on a specific folder then use rancher local path provisioner

I suggest to exec into the pod and issue the command kubectl delete pod -l=CLEARML=agent-74b23a8f --namespace=clearml --field-selector=status.phase!=Pending,status.phase!=Running --output name
sp you can see the ouput from inside the pod. This should help understand what is going on with the command

ok but describing the pod you should have, at least, the Ending cause

in values.yaml I guess apiServerUrlReference is wrong

woah.. superfast 😄

about helm chart, yes, I mean adding capability of managing a configmap qith config file. If it's interesting I can raise a PR otherwise I need to fork 😄

sorry but did you deployed in clearml namesopace?

I should add some more instruction on Github page

I finally found where the issue is, I opened an issue on gh so it's more manageable:
https://github.com/allegroai/clearml/issues/273

I also found a not so good (at least for me) behaviour:
https://github.com/allegroai/clearml/issues/272

annotations:
http://nginx.ingress.kubernetes.io/proxy-body-size: "0"
http://nginx.ingress.kubernetes.io/proxy-read-timeout: "600"
http://nginx.ingress.kubernetes.io/proxy-send-timeout: "600"

ok so we should see the call in ingress controller logs, can you pls share them?

you need a dynamic capable provisioner

output_dest works:)

About last point: I would like to retrieve the pipeline 'output_dest' and use it as a parameter in adding steps, is that possible?

ok let me check this one

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

it’s a queue used by the agent just for internal scheduling purposes

i will release a new chart version with no need to set a default storage class like I asked you to do today

so we also improved the chart, superhappy 😄

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

can you pls share how did you installed ambassador and what custom configs (if any) were applied?

it’s usually needed for autoscaler to decide when and how to scale up and down

ok so it' time to create a configmap with the entire file 😄

what kind of storageclass are you using on this one?

Did you use any override values.yaml file for this installation ?

Yes, one interesting info would be: what dynamic storage provisioner are you using? (storageclass)