I suggest to try exec into agent pod and try to do some kubectl command like a simple kubectl get pod

btw it’s an infra issue

can you pls put the entire helm list -A output command?

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

pretty strange, I also noticed in example from line 2
from clearml import TaskTypes

not totally sure tbh

yw 🙂

Hi Ofir, ty for feedback

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

yes, it should be, will test this specific behaviour to be sure

when tasks starts do you see clearml-id-* pod starting?

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

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

I don’t think it’s related how agent talk with apiserver or fileserver. It’s more related the fact agent pod internal kubectl cannot contact kubernetes apiserver

but Agents are on same k8s?

additionalConfigs: auth.conf: | auth { # Fixed users login credentials # No other user will be able to login fixed_users { enabled: true pass_hashed: false users: [ { username: "jane" password: "12345678" name: "Jane Doe" }, { username: "john" password: "12345678" name: "John Doe" }, ] } }

y ou can siply generate in UI the keys

it looks not from logs

accessing apiserver from a pod doesn’t require kubeconfig

now I’m leaving for today but let me know if it works. Have an nice day!

checking more