## Summary - Migration 34 fails with `error: the server doesn't have a resource type "rabbitmqs"` when `rabbitmqs.apps.cozystack.io` CRD does not exist on the cluster - This happens when RabbitMQ was never installed — the CRD is not present, `kubectl get` fails, and `set -euo pipefail` terminates the migration job - Added a CRD existence check before listing resources; if CRD is absent, the migration stamps the version and exits cleanly ## Test plan - [ ] Deploy a cluster without RabbitMQ installed and run migration 34 — should skip gracefully - [ ] Deploy a cluster with RabbitMQ instances without `spec.version` set — should patch them to `v3.13` - [ ] Deploy a cluster with RabbitMQ instances already having `spec.version` — should skip patching |
||
|---|---|---|
| .. | ||
| flux-aio | ||
| installer | ||
| platform | ||
| talos | ||
| testing | ||