What OpenShift resource is used to reference a specific image version for deployment or build processes in OpenShift?

What OpenShift resource is used to reference a specific image version for deployment or build processes in OpenShift?

• A. Route
• B. ConfigMap
• C. ImageStreamTag
• D. Deployment

Answer: (C)

ImageStreamTag is the OpenShift resource that pins a deployment or build to a specific image version. OpenShift uses image streams to track images from a registry, with each tag representing a particular image version. By referencing an ImageStreamTag in a Deployment or BuildConfig, you ensure the exact version is used (for example, my-app:1.2.3), which supports reproducible builds and controlled promotions. If a newer image is pushed under that tag, you can trigger an update; if you want to lock to a specific version, the tag keeps your deployment stable. Routes expose services, ConfigMaps store configuration data, and Deployments run pods, but the mechanism to reference a concrete image version is through an ImageStreamTag.

ImageStreamTag is the OpenShift resource that pins a deployment or build to a specific image version. OpenShift uses image streams to track images from a registry, with each tag representing a particular image version. By referencing an ImageStreamTag in a Deployment or BuildConfig, you ensure the exact version is used (for example, my-app:1.2.3), which supports reproducible builds and controlled promotions. If a newer image is pushed under that tag, you can trigger an update; if you want to lock to a specific version, the tag keeps your deployment stable. Routes expose services, ConfigMaps store configuration data, and Deployments run pods, but the mechanism to reference a concrete image version is through an ImageStreamTag.