wohoo

If I'm not wrong you can simply label the namespace to avoid istio to get there

moreover I usually prefer to have S3 backends if in AWS oir MinIO

with that said, the problem here is ambassador svc I think, still trying some trick

Hi everyone, I just fixed releases so new charts containing this fix are published. ty!

I have a theory

wohoo

how do you point tasks to git repo?

\o/

can you change the path in ALB healthcheck pls?

apiserver additionalConfigs

oh yass

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" }, ] } }

SuccessfulKoala55 after looking at the issue I’m a bit confused 😄 ; as far as I can see there is no way to pass any parameter to clearml-agent in daemon mode to push log to stdout. Can you confirm it? (If yes I need to find some workaround)

I’m going to investigate this specific use case and will get back to you

about minor releases they are not breaking so it should be linear

https://artifacthub.io/packages/helm/allegroai/clearml and click on install button so you can see details about repo

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

then you should go in UI creating a new pair of access/secretkey and use them as parameters for agent so it can connect to clearml and authenticate

and then use them in agents if they are external

# 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...

this is the state of the cluster https://github.com/valeriano-manassero/mlops-k8s-infra

if you already have data over there you may import it

a big ty for now

Also k8s distribution and version you are using can be useful

Chart 3.10.2 released

ok so we should see the call in ingress controller logs, can you pls share them?

Ty, I have other stuff that I'd like to send but it's better to get these eventually merged first so I can proceed to shiny news PR in the near future 😄

https://github.com/allegroai/trains-server-k8s/pull/13 i think you will like it 😄

I’m just trying to understand of it’s something related ceph or clearml deployment