⚠️ Homebrew support is being deprecated. Solo will stop publishing updates to Homebrew after August 31, 2026. Install via npm install -g @hiero-ledger/solo@latest instead. See System Readiness for full install instructions.

SOLO-2032

MinioOperatorCrdsOrphanedSoloError — System

MinioOperatorCrdsOrphanedSoloError

CodeSOLO-2032
CategorySystem
OwnershipUser
RetryableNo

Description

Thrown when the MinIO Operator’s cluster-scoped CRDs exist but no Helm release owns them. The CRDs outlive the namespace the operator was installed into, so deleting that namespace leaves them behind. Helm will not adopt resources another release created, so installing over them fails; and treating their presence as “already installed” would be worse — the operator would never run, and the Tenant resource created later would sit unreconciled with nothing pointing at the cause.

Troubleshooting Steps

  1. Delete the leftover CRDs, then run the setup again: kubectl delete crd <crdNames.join(’ ‘)>
  2. Deleting these CRDs also deletes any MinIO Tenant resources defined by them
  3. They are usually left behind when the operator namespace was deleted directly rather than through solo cluster-ref config reset