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?

Hi, atm we still didn’t tested chart against a k8s 1.29.*. That’s why we didn’t ;t included it for now; I plan to add support by this week since I’m m preparing for a new testing cluster so if you waiut a couple of day you should be good.\

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

Hi,
that's usually related IPV6/IPV4 stack configuration in your k8s cluster. Are you using just one specific stack?

h i, if I’m not wrong, mongodb doesn’t have an ARM image (and you are using a Silicon one like me ofc 😄 )

you can try use a specific image like docker.io/arm64v8/mongo:latest

agent is running the command inside the pod like you did execing into pod and manually launching it. If one is returning 127 while manually you are ok it looks to me the command issued is not the same. what is chart version you are using?

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

btw it’s an infra issue

Hi, in k8s autoscaling must be managed by cloud pro user autoscaler. When the clearml-agent bound to related queue will spawn a new task pod with configured resources, k8s will adapt. On AWS you can start here https://docs.aws.amazon.com/eks/latest/userguide/autoscaling.html

probably
is not accessible from your pod

clearml and agent are in the same namespace?

ok let me check this one

I can add some configurable value then ASAP 👍 will do in next days

ok, will try to find a solution then, ty

I need to evaluate a better way to handle image versioning for the future, btw latest version should be fixed. Apologies folks!

# Point to the internal API server hostname APISERVER= `

Path to ServiceAccount token

SERVICEACCOUNT=/var/run/secrets/kubernetes.io/serviceaccount

Read this Pod's namespace

NAMESPACE=$(cat ${SERVICEACCOUNT}/namespace)

Read the ServiceAccount bearer token

TOKEN=$(cat ${SERVICEACCOUNT}/token)

Reference the internal certificate authority (CA)

CACERT=${SERVICEACCOUNT}/ca.crt

Explore the API with TOKEN

curl --cacert ${CACERT} --header "Authorization: Bearer ${TOKEN}" -X GET ${A...

I mean this blob is then saved on the fs

yaya confirmed

how do you point tasks to git repo?

and I will give you feedback here

AgitatedDove14 maybe you can check also --version that returns the help menu

uh, using clearml-task params 😄

today I'm in the middle of sprint plannings for my team so I will not be probably fast to help if needed, but feel free to ping me just in case (I will try to do my best)

clearml --help says
--version Display the clearml-task utility version

woah.. superfast 😄

great 😄

you can create a specific config like one in https://clear.ml/docs/latest/docs/integrations/storage/

accessing apiserver from a pod doesn’t require kubeconfig

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