Which resource is typically used to deploy applications with rolling updates in OpenShift 4?

Which resource is typically used to deploy applications with rolling updates in OpenShift 4?

• A. DaemonSet
• B. StatefulSet
• C. Job
• D. Deployment

Answer: (D)

Rolling updates in OpenShift 4 are handled by a Deployment. A Deployment describes the desired state for a set of pods and, when you update the pod template (for example, changing the image), it creates a new ReplicaSet and performs a rolling rollout. This means old pods are gradually replaced with new ones, while the system preserves the requested number of available pods. The default RollingUpdate strategy lets you tune the update pace with settings like maxUnavailable and maxSurge to balance speed and availability. DaemonSet targets a pod on every node and is used for node-level agents rather than general app updates. StatefulSet is for stateful workloads with stable identities and ordered startup/shutdown, and Job runs to completion for batch tasks. So the typical resource for deploying applications with rolling updates is the Deployment.

Rolling updates in OpenShift 4 are handled by a Deployment. A Deployment describes the desired state for a set of pods and, when you update the pod template (for example, changing the image), it creates a new ReplicaSet and performs a rolling rollout. This means old pods are gradually replaced with new ones, while the system preserves the requested number of available pods. The default RollingUpdate strategy lets you tune the update pace with settings like maxUnavailable and maxSurge to balance speed and availability. DaemonSet targets a pod on every node and is used for node-level agents rather than general app updates. StatefulSet is for stateful workloads with stable identities and ordered startup/shutdown, and Job runs to completion for batch tasks. So the typical resource for deploying applications with rolling updates is the Deployment.