About clearml-agent chart - it stucks in init state for a long time, do you have an idea, why it could be so?

Yeah, that worked! . Thanks a lot!

pls upgrade agent chart to just released 1.0.2

yes

later in the day I will push also a new clearml chart that will not contain anymore k8s glue since it’s now in clearml-agent chart, this is why I was suggesting to use that chart :)

Why do you have the bucket separate?

running tests

can you pls check logs of init-container?

ok let me check this one

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

PR incoming

It worked, thanks!

JuicyFox94 , SuccessfulKoala55 sorry to bother you again, question about minio still raises - I tried different ways to configure it in additionalConfigs, and unfortunately does not succeeded. Here are several examples I tried:

clearml and agent are in the same namespace?

this is the PR: https://github.com/allegroai/clearml-helm-charts/pull/80 https://github.com/allegroai/clearml-helm-charts/pull/80 will merge it soon so agent chart 1.0.1 will be released

clearml-agent 1.1.0 released

in values.yaml I guess apiServerUrlReference is wrong

Now seems I’ve got 403/405 on fileserver
+ curl -sw %{http_code} ` -o /dev/null

• [ 405 -ne 403 ]
• echo waiting for fileserver
• sleep 5 `

if you do a kubectl get svc in namspace you should see the svc of api webserver and fileserver

ReassuredArcticwolf33 PR is coming https://github.com/allegroai/clearml-helm-charts/pull/84

pls give me 10 minutes

my one, for example is http://clearml-apiserver:8008

Wait, JuicyFox94 , is there an additionalConfigs value in the agent chart values? I can't find it there...

Let me check and I will eventually get back with a PR

ReassuredArcticwolf33 pls try this one and let me know if this is working for you

chart-agent 1.0.1 released

You should have a single setting for the minio server

but what base field should it be? clearml.conf?

oh I got what the problem is