ok, for mayor version upgrade my suggestion is to backup the data somewhere and do a clean install after removing the pvc/pv

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

ok, ty very much for your feedback 😄

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

happy to hear that

it’s a queue used by the agent just for internal scheduling purposes

I absolutely need to improve the persistence part of this chart 😄

btw I think it's related clearml-task usage; did you try to create a pipeline with decorators creating it with clearml-task before?

In this case I suggest to give a try to k8s-glue that is there by default in latest chart version

and are you sure you mongodb respawned on same node?

our data engineer directly write code in pycharm and test it on the fly with brakpoints. when good we simply commit in git and we set a tag "prod ready"

probably
is not accessible from your pod

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

Just one more info: atm I tested Elastic v7.10.* . I still didn't tested 7.11-7.12-7.13

😄

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

ops

so do you want to mount files into agent 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"...

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

this is a connection fail from agent to apiserver. the flow should be aget-pod -> apiserver svc -> apiserver pod. maybe also apiserver can have something in ogs that can be checked

this sounds weird to me