Which OpenShift object is responsible for managing the rollout of Pods and tracking their versions?

• A. Deployment
• B. ImageStream
• C. Route
• D. PersistentVolume

Answer: (A)

Rollouts and version tracking for Pods are handled by a Deployment. A Deployment defines the desired number of replicas, the Pod template, and the rollout strategy. When you update the Pod template, the Deployment creates a new ReplicaSet for the new version and gradually shifts traffic from the old ReplicaSet to the new one using a rolling update, ensuring a controlled transition. This process inherently tracks versions, since each revision of the Pod template corresponds to a new ReplicaSet and a point-in-time rollout, which you can inspect or roll back if needed. In OpenShift, Deployment is the standard resource for managing ongoing rollouts and versions, while other objects like Route, ImageStream, or PersistentVolume serve different roles—exposing services, tracking image versions, or providing storage, respectively.