A team marks a ConfigMap as immutable after validating its data. What is the primary operational effect?
Select an answer to reveal the explanation.
Short Explanation
Immutable means the ConfigMap is freeze-dried — no more in-place edits. Need a change? Ship a new object and point the workload at it. That lock prevents casual overwrites of known-good config.
Full Explanation
Setting immutable: true on a ConfigMap prevents updates to its data (and related mutable fields per API rules). Teams that need changes create a new ConfigMap and retarget workloads, which pairs well with explicit rollouts. Immutability does not change the object into a Secret or alter mount eligibility by namespace. It is a safeguard against accidental mutation of configuration consumed by applications.