Which Kubernetes resource uses immutable: true boolean field?

Deployments are designed to be updated via strategies like rolling updates, so they do not have an `immutable` field for their entire configuration.

Pods can be replaced or recreated, but the Pod resource itself does not have an `immutable` field to lock its definition after creation; changes typically lead to recreation.

A `ConfigMap` can be marked as immutable by setting `immutable: true` in its manifest, which ensures that its data cannot be changed or deleted after creation. This feature enhances security and reliability by preventing runtime modifications to critical configuration data, ensuring consistency for dependent applications.

ReplicaSets ensure a stable set of running Pods, and while their template can be updated, the ReplicaSet resource itself does not have an `immutable` field to prevent modifications.