platform: backupstrategy-controller can't upgrade from v1.6.4, new Strategy CRDs come in the same release as their CRs #4925

What is wrong?

On upgrade from v1.6.4 to v1.7.0-rc.1 HelmRelease backupstrategy-controller stays in UpgradeFailed, and retry every 30s doesn't help:

Helm upgrade failed for release cozy-backup-controller/backupstrategy-controller: [resource mapping not found for name: "cozy-default-kafka" namespace: "" from "": no matches for kind "Kafka" in version "strategy.backups.cozystack.io/v1alpha1"
ensure CRDs are installed first, resource mapping not found for name: "cozy-default-rabbitmq" namespace: "" from "": no matches for kind "Rabbitmq" ...
resource mapping not found for name: "cozy-default-redis" ... no matches for kind "Redis" ...]

None of the new CRDs from definitions/ (kafka, mongodb, rabbitmq, redis) exist on the cluster, only 7 strategy CRDs from v1.6.4 are there.

I think the chart renders CRDs through templates/crds.yaml (glob over definitions/*.yaml) in the same release as strategy-*-default.yaml CRs. Helm resolves kinds of all objects before applying any, so release that adds a new Strategy kind can't be upgraded, and CRDs never get created. Fresh install not tested.

Environment

Cozystack v1.6.4 -> v1.7.0-rc.1, isp-full variant.

How it should work?

Upgrade creates the new CRDs first, so default strategies are created and the release goes Ready.