What does the oc set image command do and how can it trigger a rollout?

• A. Deletes the deployment and recreates it.
• B. Creates a new BuildConfig from an image.
• C. Updates the image of a container within a resource; a change can trigger a new rollout if the image field is updated and rollout is configured.
• D. Changes the service selector to match a new image.

Answer: (C)

Updating the image reference in a resource’s Pod template is what this command does. When you run it, you point a container in a DeploymentConfig, Deployment, or similar resource to a new image (for example, a new tag). If the resource is set up to react to image changes—such as an OpenShift DeploymentConfig with an image-change trigger or a Kubernetes Deployment whose rollout is configured to roll out on template changes—the system will start a new rollout using the new image. In short, changing the image field can automatically kick off a rollout, but only if the deployment is configured to trigger on image updates. It doesn’t delete or recreate resources, doesn’t create a BuildConfig, and doesn’t modify the service selector.