What is a common pattern to implement CI/CD for apps running on OpenShift using built-in resources?

What is a common pattern to implement CI/CD for apps running on OpenShift using built-in resources?

• A. Use a combination of BuildConfig/ImageStreams, Deployments, and OpenShift Pipelines (Tekton) for CI/CD flows.
• B. External CI tools only.
• C. Rely solely on Deployments.
• D. Use only Secrets.

Answer: (D)

OpenShift-native CI/CD relies on a cohesive set of built-in resources to automate the full flow from code change to deployment. A typical pattern uses BuildConfig to define how the application is built into a container image, ImageStreams to track and tag those images, and Deployments to run the updated image in the cluster. OpenShift Pipelines (built on Tekton) adds end-to-end automation for the steps—lint, test, build, push, and deploy—so you can run a complete pipeline inside the cluster and trigger it from code changes or image updates. This integrated approach gives you repeatable, secure, and scalable CI/CD using the platform’s own tools rather than relying solely on external services. External CI tools can complement this, but the built-in pattern described here provides the full, cluster-resident workflow. Deployments alone don’t handle building or pipeline orchestration, and Secrets alone don’t implement the CI/CD process.

OpenShift-native CI/CD relies on a cohesive set of built-in resources to automate the full flow from code change to deployment. A typical pattern uses BuildConfig to define how the application is built into a container image, ImageStreams to track and tag those images, and Deployments to run the updated image in the cluster. OpenShift Pipelines (built on Tekton) adds end-to-end automation for the steps—lint, test, build, push, and deploy—so you can run a complete pipeline inside the cluster and trigger it from code changes or image updates. This integrated approach gives you repeatable, secure, and scalable CI/CD using the platform’s own tools rather than relying solely on external services.

External CI tools can complement this, but the built-in pattern described here provides the full, cluster-resident workflow. Deployments alone don’t handle building or pipeline orchestration, and Secrets alone don’t implement the CI/CD process.