Which OpenShift resource stores versions of container images and provides a stable reference for deployments?

Which OpenShift resource stores versions of container images and provides a stable reference for deployments?

• A. Secret.
• B. ConfigMap.
• C. ImageStream.
• D. PersistentVolume.

Answer: (C)

Image streams in OpenShift provide a stable handle for container images by storing and versioning image references. An ImageStream holds tags like myapp:1.2 or myapp:latest, representing specific image versions. Deployments can reference these imageStreamTag values, so they point to a consistent image even if the underlying image in the registry changes. When a new image is built or pushed, you can trigger a deployment to use the updated tag, while existing deployments can keep using the same reference until you choose to update it. This separation between image identity and deployment ensures predictable, versioned deployments. Secrets and ConfigMaps store configuration or sensitive data, not container images, and PersistentVolume provides storage for data. They don’t offer image versioning or a stable deployment reference.

Image streams in OpenShift provide a stable handle for container images by storing and versioning image references. An ImageStream holds tags like myapp:1.2 or myapp:latest, representing specific image versions. Deployments can reference these imageStreamTag values, so they point to a consistent image even if the underlying image in the registry changes. When a new image is built or pushed, you can trigger a deployment to use the updated tag, while existing deployments can keep using the same reference until you choose to update it. This separation between image identity and deployment ensures predictable, versioned deployments.

Secrets and ConfigMaps store configuration or sensitive data, not container images, and PersistentVolume provides storage for data. They don’t offer image versioning or a stable deployment reference.