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 `
About clearml-agent chart - it stucks in init state for a long time, do you have an idea, why it could be so?
my one, for example is http://clearml-apiserver:8008
but what base field should it be? clearml.conf?
Wait, JuicyFox94 , is there an additionalConfigs
value in the agent chart values? I can't find it there...
Yeah, that worked! . Thanks a lot!
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:
ReassuredArcticwolf33 PR is coming https://github.com/allegroai/clearml-helm-charts/pull/84
pls upgrade agent chart to just released 1.0.2
ReassuredArcticwolf33 pls try this one and let me know if this is working for you
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 :)
I’m just going to include these credentials in pod template too
in values.yaml I guess apiServerUrlReference is wrong
You should have a single setting for the minio server
if you do a kubectl get svc in namspace you should see the svc of api webserver and fileserver
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