Alfredo Funicello

> Don't use on cluster in this case, if you put init script on every node it will be executed automatically. Alternatively, you can do it on a first node...

any updates on this?

My workaround using ansible atm: ``` - name: Stopping until cluster is ready kubernetes.core.k8s_info: kind: ClickHouseInstallation name: chi register: result until: result.resources | json_query('[*].status.status') | select('match','Completed') | list | length...

> Look to https://github.com/Altinity/clickhouse-operator/blob/master/docs/chi-examples/20-protobuf-schema-example.yaml I think this has some errors. Both in practice since the volumes are not declared and the code as is won't start, both in theory since...

@Slach > `chi-protobuf-example-common-configd` means configmap name which generated by `clickhouse-operator` > so, if you change your metadata name from protobuf-example to other you need to change this name in manifest...

Ah, sorry for leaving those out. We're building on Kubernetes with Docker and trying to pair with a mysql instance. We also installed the pdo_mysql adding it to the custom...

Yes that's exactly what we're doing. I understand the principle of statelessness but would you mind expanding on the reason this image would not support an external database? We decided...

bump @nagimov; any info about the curl cacert?

> Regarding the cert issue, I'm not sure what causes this. The image pulls the `https://curl.se/ca/cacert.pem` file and places it to `/etc/ssl/certs`, so pretty much the same as your fix...

@nagimov > Could you try adding `chmod` into your Dockerfile? That works, the image native `cacert.pem` can't be accessed from the user `www-data` which is completely breaking for the image,...