Building-permits platform engineers consider deleting a CRD while custom resource instances still exist. What operational caution applies?
Select an answer to reveal the explanation.
Short Explanation
Deleting a CRD while instances exist is like shredding the form template while filed permits still reference it—messy and often destructive. Treat CRD removal as a breaking API change. Clean up or migrate instances with a plan first.
Full Explanation
When a CRD is deleted, associated custom resources are typically removed according to API extension behavior, which can destroy application state unexpectedly. Administrators should treat CRD removal as a breaking change: drain or migrate CRs, confirm operator dependencies, then delete. It is not a no-op on existing instances.