Which steps define a simple OpenShift Pipeline (Tekton) to build and deploy on push?

Prepare for the Red Hat Openshift Developer EX288 Exam. Study with comprehensive quizzes and flashcards. Each question includes hints and explanations to enhance your understanding. Ace your exam with confidence!

Multiple Choice

Which steps define a simple OpenShift Pipeline (Tekton) to build and deploy on push?

Explanation:
OpenShift Pipelines (Tekton) orchestrate work by defining a Pipeline as a sequence of Tasks and then running that Pipeline with a PipelineRun. To build and deploy on push, you set up a Pipeline that includes two Tasks: one that handles the build (creating an artifact or container image) and another that handles deployment to the cluster. A PipelineRun starts this workflow, pulling in the necessary inputs and producing outputs. Referencing a Git resource provides the source code from the repository, while cluster resources supply the targets and credentials needed for the build and deployment (such as the image registry and the deployment configuration). With a push event, a Trigger can kick off the PipelineRun automatically, making the process responsive to code changes. The other options describe deploying or packaging steps that aren’t expressed as a Tekton Pipeline, so they don’t capture the push-driven build-and-deploy automation this approach enables.

OpenShift Pipelines (Tekton) orchestrate work by defining a Pipeline as a sequence of Tasks and then running that Pipeline with a PipelineRun. To build and deploy on push, you set up a Pipeline that includes two Tasks: one that handles the build (creating an artifact or container image) and another that handles deployment to the cluster. A PipelineRun starts this workflow, pulling in the necessary inputs and producing outputs. Referencing a Git resource provides the source code from the repository, while cluster resources supply the targets and credentials needed for the build and deployment (such as the image registry and the deployment configuration). With a push event, a Trigger can kick off the PipelineRun automatically, making the process responsive to code changes. The other options describe deploying or packaging steps that aren’t expressed as a Tekton Pipeline, so they don’t capture the push-driven build-and-deploy automation this approach enables.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy