feat: add ImageCatalog.componentImages from CNPG 1.30.0

[timgriffiths]

PR Checklist

• I generated these CRs using the CRD Extractor tool. If I used a different method, I have described the method in this PR.
• I am updating existing schemas and have specified the updated schema version.
• I am adding new schemas and included a link to the GitHub repository that contains the source of these schemas.

Updated schema version: CloudNativePG 1.30.0 (Helm chart cloudnative-pg 0.29.0).

Source CRDs: https://github.com/cloudnative-pg/cloudnative-pg/tree/v1.30.0/config/crd/bases

Release: https://github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.0

Method

I did not extract from a live cluster. I converted the official v1.30.0 CRDs with the same openapi2jsonschema.py script the CRD Extractor uses:

postgresql.cnpg.io_imagecatalogs.yaml
postgresql.cnpg.io_clusterimagecatalogs.yaml

What changed

CNPG 1.30.0 added spec.componentImages so a Pooler can pin the PgBouncer image via spec.pgbouncer.imageCatalogRef (cloudnative-pg#10568). The catalog schemas still have additionalProperties: false on spec and only allow images, so kubeconform rejects any ImageCatalog that sets componentImages.

This updates:

• postgresql.cnpg.io/imagecatalog_v1.json
• postgresql.cnpg.io/clusterimagecatalog_v1.json (same spec)

Also picks up the 1.30.0 extensions[].name maxLength: 59 clarification from the same CRDs. Other CNPG resources were left unchanged.

Made with Cursor