What resources are commonly created automatically when you run oc new-app against a Git repository?

What resources are commonly created automatically when you run oc new-app against a Git repository?

• A. BuildConfig, ImageStream, and Deployment
• B. DeploymentConfig and ImageStream
• C. Job, Build, and Service
• D. Deployment, Route, and ConfigMap

Answer: (A)

Running oc new-app on a Git repository starts a small, self-contained source-to-image flow. It creates a BuildConfig to build the application from the repository, an ImageStream to store and track the resulting image, and a Deployment to run the application pods using that image. This trio sets up the core pipeline: the BuildConfig defines how to build, the ImageStream holds the built image, and the Deployment launches and manages the running instances of the app. A Service may be created to expose the app, but the essential automatic trio that OpenShift commonly generates is these three resources.

Running oc new-app on a Git repository starts a small, self-contained source-to-image flow. It creates a BuildConfig to build the application from the repository, an ImageStream to store and track the resulting image, and a Deployment to run the application pods using that image. This trio sets up the core pipeline: the BuildConfig defines how to build, the ImageStream holds the built image, and the Deployment launches and manages the running instances of the app. A Service may be created to expose the app, but the essential automatic trio that OpenShift commonly generates is these three resources.