Which OpenShift command would deploy an image from Quay into a new deployment config with a specific name?

Which OpenShift command would deploy an image from Quay into a new deployment config with a specific name?

• A. oc new-app --as-deployment-config --name name --docker-image quay.io/path/name:ver
• B. oc new-app --name name --docker-image quay.io/path/name:ver
• C. oc new-app --as-deployment-config --name name --image quay.io/path/name:ver
• D. oc new-app --as-deployment --name name --docker-image quay.io/path/name:ver

Answer: (A)

Creating a DeploymentConfig from a specific image in OpenShift is done with a single command that combines three elements: the instruction to produce a DeploymentConfig, the explicit name for that resource, and the image reference to pull from Quay. The key is using the option that forces a DeploymentConfig to be created, so OpenShift builds a deployment config rather than a Kubernetes Deployment. Providing the name sets exactly what the deployment config will be called. Pointing to the image with the docker-image reference tells OpenShift which image to deploy and with which tag. When you put these together, you get a new DeploymentConfig named as requested that uses the Quay image quay.io/path/name:ver for its pods. The other choices miss one or more of these pieces: they either don’t request a DeploymentConfig at all, would create a different kind of resource (a Deployment), or use a different image flag that doesn’t guarantee the same result.

Creating a DeploymentConfig from a specific image in OpenShift is done with a single command that combines three elements: the instruction to produce a DeploymentConfig, the explicit name for that resource, and the image reference to pull from Quay.

The key is using the option that forces a DeploymentConfig to be created, so OpenShift builds a deployment config rather than a Kubernetes Deployment. Providing the name sets exactly what the deployment config will be called. Pointing to the image with the docker-image reference tells OpenShift which image to deploy and with which tag. When you put these together, you get a new DeploymentConfig named as requested that uses the Quay image quay.io/path/name:ver for its pods.

The other choices miss one or more of these pieces: they either don’t request a DeploymentConfig at all, would create a different kind of resource (a Deployment), or use a different image flag that doesn’t guarantee the same result.