A developer proposes storing a 50Mi proprietary binary installer inside a ConfigMap for a batch Job. What guidance best matches ConfigMap purpose and practical limits?
Select an answer to reveal the explanation.
Short Explanation
ConfigMaps are sticky notes and short settings files — not a freight elevator for fat binaries. Park large artifacts in the image or object storage. etcd-backed objects have real size limits and the wrong shape for installers.
Full Explanation
ConfigMaps are intended for configuration material and have practical size limits enforced by the API server and etcd. Large binaries belong in container images, volumes backed by appropriate storage, or external artifact repositories. Secrets are for sensitive data, not a workaround for oversized binaries. Immutability does not raise those size constraints.