Which resource is used to define automated builds from source or image into a deployable image?

Which resource is used to define automated builds from source or image into a deployable image?

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

Answer: (B)

OpenShift uses a BuildConfig to define how to turn source code or an existing image into a deployable image. A BuildConfig specifies the build strategy (Source for building from code, or Docker for building from a Dockerfile), where to pull the input from, and where to push the resulting image (usually to an ImageStreamTag). When automatic triggers are enabled, changes to the source repository or to the base image can automatically start a new build, producing a fresh image without manual steps. The ImageStream stores and tags the built image, but it doesn’t define the build process itself. Routes expose services, and Deployments manage running pods, but neither defines automated image builds.

OpenShift uses a BuildConfig to define how to turn source code or an existing image into a deployable image. A BuildConfig specifies the build strategy (Source for building from code, or Docker for building from a Dockerfile), where to pull the input from, and where to push the resulting image (usually to an ImageStreamTag). When automatic triggers are enabled, changes to the source repository or to the base image can automatically start a new build, producing a fresh image without manual steps. The ImageStream stores and tags the built image, but it doesn’t define the build process itself. Routes expose services, and Deployments manage running pods, but neither defines automated image builds.