so you installed chart version 3.10.1

Hey ApprehensiveSeahorse83 , I didn’t forget about you, it’s just a busy time for me; will answer during the day after a couple of more tests on my testing env.

can you pls check logs of init-container?

with that in place k8s should be able to provisione pvc

so you are using docker-compose?

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

(probably it's not possible)

it will be easier for me to reproduce

I need to investigate, ScrawnyLion96 can you pls open an issue on https://github.com/allegroai/clearml-helm-charts ?

AgitatedDove14 trainsConfig is totally optional and you can put the config file itself in it.. e.g.:
` trainsConfig: |-
sdk {
aws {
s3 {
key: ""
secret: ""
region: ""
credentials: [
{
host: "minio.minio:9000"
key: "DEMOaccessKey"
secret: "DEMOsecretKey"
...

it looks not from logs

yw 🙂

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?

btw it’s an infra issue

Maybe it can be enough to set annotations in ingress section

an implementation of this kind is interesting for you or do you suggest to fork? I mean, I don't want to impact your time reviewing

it should be ok, for dependency charts (mongodb/elastic/redis) you need to check values by the owner (link is in valus.yaml sections)

atm it’s the way to go

This is specific K8s infra management, usually I use Velero for backup

s o kubectl -n clearml get ingress

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

oh yass

btw in k8s we abandoned the usage of services since it’s not needed anymore. you can put an agent consuming a queue and enqueue task to it

apiserver: additionalConfigs: services.conf: |should be
apiserver: additionalConfigs: apiserver.conf: |in this way he pod will mount a file called apiserver.conf instead of services.conf that is not the right filename for auth.

if you have problems with other images I suggest to run docker in emulation mode so you can run amd64 images

not official but should work

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

it’s weird, can you pls open a bug in clearml-helm-charts repo?

You can’t write on readonly replica is about MongoDB. I guess you are using a multiple replica setup. In this case the mongodb dependency chart have a lot of parameters to tweak the system and maybe also an arbiter is good for you. But this is a huge topic regarding mongodb specific k8s setups.

Will try to reproduce in next couple of hours, will give you feedback here asap