Philippe Scorsolini

So, currently we create a dedicated role, then for all the accessible databases we create the function and grant that role access to it. Are you suggesting we create the...

I opted for adding a field `AutDBName`, setting it results in the automatic configuration not being applied, same as we do for `AuthQuery` and `AuthQuerySecret`.

Less is more! ✂️

I think client caching also has another issue, so while at it, might be worth addressing that too: if one gets the client, modifies the kubeconfig or any other client...

> > Drawback being that the client will be recreated every time it is accessed with `config.Client()` > > > > I am personally not afraid of the performance costs...

Good catch, thanks! But it looks like we are also missing a few other ones, no? I think it's because at some point we switched to deploying them by default...

ok, now i got it, it's in sync with the default ones we deploy with manifests, see https://github.com/cloudnative-pg/cloudnative-pg/blob/main/releases/cnpg-1.20.0.yaml#L12160. The ones you are adding come from the example one: https://github.com/cloudnative-pg/cloudnative-pg/blob/main/docs/src/samples/cluster-example-monitoring.yaml#L27. I'm...

Yes, either by adding or removing these everywhere. I'm checking if there was a reason not to include them in the default queries, i'll let you know 🙏

https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.28/#securitycontext-v1-core > May also be set in PodSecurityContext. If set in both SecurityContext and PodSecurityContext, the value specified in SecurityContext takes precedence. Isn't it equivalent?

Hi @npdgm! Thanks a for your contribution. Just to make sure, this is going to affect only the operator's metrics, not the Clusters' ones, that's what you wanted right?