A platform team offers a validated custom API for provisioning caches, while another team only needs a few key/value settings for one app. When is a CRD the better fit than a ConfigMap?
Select an answer to reveal the explanation.
Short Explanation
ConfigMaps are sticky notes of settings; CRDs are formal forms backed by an Operator’s brains. Use the CRD when the platform exposes that structured API. Keep ordinary app kv config in ConfigMaps.
Full Explanation
ConfigMaps store configuration data for applications. CRDs define new typed APIs, typically paired with Operators that enforce schema and reconcile complex systems. Choose a CR when consuming an Operator’s extended API; use a ConfigMap for ordinary application settings. String length, node count, and static-HTML rules are not the decision criteria.