What is the primary purpose of an ImageStream in OpenShift, and how is it used by a Deployment?

• A. An ImageStream stores and tracks image versions in OpenShift.
• B. An ImageStream defines how services are exposed to the outside world.
• C. An ImageStream provides storage for persistent data.
• D. An ImageStream aggregates logs from containers.

Answer: (A)

ImageStreams in OpenShift provide a way to store and track image versions within the cluster. They act as a local, tag-based view of container images, so deployments don’t have to point to a specific registry URL or digest. By using an ImageStreamTag (like myapp:latest) in a Deployment, the pod template references the image through the stream, and OpenShift resolves it to the actual image when pulling the container.

This arrangement enables versioning and smooth updates: when you push a new image and update the ImageStreamTag, the deployment can be triggered to roll out the new image, or you can promote a newer tag to production. It also supports rollbacks by switching the ImageStreamTag back to an earlier image version. In short, ImageStreams decouple application deployments from exact image locations and provide centralized image versioning and update capability.

The other options describe different features: exposing services to the outside world is handled by routes and services, persistent data storage is managed with persistent volumes, and logs are collected by logging tools. These are not the purpose of an ImageStream.