A 311 Operator ships a new CRD version and marks the old one deprecated. How should the application team that owns Custom Resources respond?
Select an answer to reveal the explanation.
Short Explanation
When the Operator authors retire a CRD version, your CRs are like forms that must match the new template. Update the Custom Resource specs to the supported version and follow their migration guidance. Clinging to the deprecated shape is how apply and reconcile start failing.
Full Explanation
Operators expose CustomResourceDefinitions with versioned schemas. When authors deprecate a CRD version, consuming applications must migrate their Custom Resources to a supported version, adjusting fields as the Operator’s release notes require. ConfigMaps are not a substitute for CRD-backed automation, and forcing perpetual Operator downgrades is not sustainable application maintenance.