Which resource pair is commonly used together to track image versions and drive deployment updates in OpenShift pipelines?

Which resource pair is commonly used together to track image versions and drive deployment updates in OpenShift pipelines?

• A. ImageStreams and Deployments.
• B. Secrets and ConfigMaps.
• C. PersistentVolumes and Services.
• D. Routes and Ingresses.

Answer: (A)

OpenShift pipelines rely on ImageStreams to track specific image versions and Deployments to manage running pods that use those images. In a typical flow, a new build pushes an updated image into an ImageStreamTag, and the corresponding Deployment references that same ImageStreamTag as its container image. When the tag changes, the deployment can roll out with the new image, keeping the running application in sync with the latest build. This pairing lets you version images and automatically drive deployment updates through the pipeline. The other options focus on configuration data (Secrets and ConfigMaps), storage and networking (PersistentVolumes and Services), or external exposure (Routes and Ingress), none of which directly handle tracking image versions or triggering deployments.

OpenShift pipelines rely on ImageStreams to track specific image versions and Deployments to manage running pods that use those images. In a typical flow, a new build pushes an updated image into an ImageStreamTag, and the corresponding Deployment references that same ImageStreamTag as its container image. When the tag changes, the deployment can roll out with the new image, keeping the running application in sync with the latest build. This pairing lets you version images and automatically drive deployment updates through the pipeline. The other options focus on configuration data (Secrets and ConfigMaps), storage and networking (PersistentVolumes and Services), or external exposure (Routes and Ingress), none of which directly handle tracking image versions or triggering deployments.