Philippe Scorsolini
Philippe Scorsolini
I have it implemented [here](https://github.com/phisco/crossplane/tree/xrd-validation), but it's based on #4128 given that there was obviously some overlap there, so I'll hold on waiting for that to get in first.
See also https://docs.crossplane.io/v1.14/concepts/packages/#the-crossplaneyaml-file for more context.
Relying on an annotation would mean cnpg would have to interact with the registry directly?
I thought https://github.com/cloudnative-pg/cloudnative-pg/pull/3711 was related to this. Am I missing something? However, I would vote for an additional field specifying the version, if not provided we can try inferring the...
Looks like these could be definitely added to the default metrics: https://github.com/cloudnative-pg/cloudnative-pg/blob/main/config/manager/default-monitoring.yaml I'll let the pg experts check we are not already exposing these info in some other form 😉...
Edit: I think we already expose `pg_settings_*`. My only doubt is on the `pg_stat_activity_count`
/test limit=local
This is actually an issue with the helm chart not properly configuring the certificate directory when mutating webhooks are disabled
FYI, this doesn't apply anymore with https://github.com/crossplane-contrib/function-environment-configs, as we don't have `.spec.environment.environmentConfigs`, but just `.environmentConfigs` in the input of the step.
@negz totally agree: https://github.com/crossplane/crossplane/pull/3637