Thomas Decaux

Yeah I agree, the percona users setup is ... no sense https://github.com/percona/percona-xtradb-cluster-operator/blob/main/build/pxc-entrypoint.sh#L398 In my opinion, the operator: - must create all percona users it-self - reconciliate root password With my...

> https://github.com/percona/percona-xtradb-cluster-operator/blob/main/build/pxc-entrypoint.sh#L398 Well, there is already "reconcile" users feature here https://github.com/percona/percona-xtradb-cluster-operator/blob/main/pkg/controller/pxc/users.go#L47 Yes I use argo workflow to setup percona users.

> I don't know why CLA check is pending, @hors please merge when you have the chance. when clicking on CLA check:

> this one you mean? > > ``` > affinity: {} > fullnameOverride: "" > image: "" > imagePullPolicy: IfNotPresent > imagePullSecrets: null > nameOverride: "" > nodeSelector: {} >...

never cache a secret .......

> What is the risk if this is turned off? Let's say I create separate `master` and `data` node PDBs. PDB ensure a minimum pods always exist. There is no...

the solution will not work if you use a keystore ! Because operator append an initContainer before the permissions container ....

As I wrote on https://github.com/elastic/cloud-on-k8s/issues/7100 , elastic should copy as much as possible what prometheus/grafana are doing with kubernetes! - a simple ConfigMap to define grafana dashboard - PrometheusRule CRD...

> I have no idea what you did there, but you are a boss if you fix this bloody message that is flooding the logs. 👍 > > Ping @jolelievre...

Ola, did a very simple fix >>> https://github.com/PrestaShop/PrestaShop/pull/35466