I wouldn’t say it’s related RBAC because the issue seems Networking realted so connection timed out

Hi, helm show readme should output informations on any single parameter fo the chart. helm show values will show the entire values file containing also the structure.

wohoo

but I can be wrong, give me 30 mins while I recreate same local installation with samecchart so I can see if something is wrong

with the right svc names

You are not cheating 😂

adding @<1523701087100473344:profile|SuccessfulKoala55> to the conversation because I’m not totally sure the problem relies on ingress, it looks to be a bad token but it shouldn’t since init was good

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.

let me check

try this into the pod

` apiserver:
additionalConfigs:
services.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"...

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

or maybe default?

this means network issues at some level

I'm going to ask an update to docs

In fact it's the same we are applying to helm charts for k8s

as usual it starts small and after 5 mins discussion is getting challenging 😄 I love this stuff... let me think a bit about it I will get back to you asap on this.

Hi @<1523701717097517056:profile|ScantMoth28> , disabling atm we are not supporting Istio but I’m more than willing to look at a proposal like yours. Let’s discuss this on a new issue on github pls so we can keep track of it and find a good way to implement. thanks

thanks for letting us know, I took a n ote for more tests on liveness, ty again!

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

not a big issue but you maybe worth a quick fix

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

there’s a PR coming with example values: https://github.com/allegroai/clearml-helm-charts/pull/234

Hi, not really sure if these is any problem with Github CDN but it looks fine to me right now: https://github.com/allegroai/clearml-helm-charts/issues/155

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

btw, judging from screenshots services are ok but pod are not up, especially elastic, redis and mongodb are Pending so it means k8s didn’t scheduled them for some reason you can find describing these pods

but it;s just a quick guess, not sure if i’m right

you can workaround the issue mlunting the kubeconfig but I guess the issue is someway to be investigated

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

I don’t think you need to pass these env vars in extraenvs, references are automatically generated by chart. After removing them, pls post webserver pod logs here and let’s see if we can spot the issue, ty.