what kin d of Clearml installation you did on machine? there are processes listening on these ports?

if it turns 503 it’s not network but something on top of it

(probably it's not possible)

ok so they are executed as expected

Hi,
how did you specified it in Helm override file?

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 :)

oh now I understand

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

so you should be able to pass additional stuff in this field directly during Helm apply

hopefully this will fix the issue

wohoo

ok so you are on chart major verison 4 while we are now on 6. Let me check one minute pls

just a couple of info

Exactly, these are system accounts

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

About nodeSelector you are right, one is for the agent pod while the other is used to spawn task pods

but Agents are on same k8s?

internal migrations are directly done by apiserver on startup

not official but should work

you need to investigate why it’s still in Pending state

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

oh wait 😄

Also k8s distribution and version you are using can be useful

https://github.com/allegroai/clearml-helm-charts/blob/9c15a8a348898aed5504420778d0e815b41642e5/charts/clearml/values.yaml#L86

ty

pls upgrade agent chart to just released 1.0.2

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

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

this will make autoscaler life easier knowiing exactly how much resources you need

Maybe it can be enough to set annotations in ingress section