×

Red Hat OpenShift Pipelines is a cloud-native CI/CD experience based on the Tekton project which provides:

  • Standard Kubernetes-native pipeline definitions (CRDs).

  • Serverless pipelines with no CI server management overhead.

  • Extensibility to build images using any Kubernetes tool, such as S2I, Buildah, JIB, and Kaniko.

  • Portability across any Kubernetes distribution.

  • Powerful CLI for interacting with pipelines.

  • Integrated user experience with the Developer perspective of the OpenShift Container Platform web console.

For an overview of Red Hat OpenShift Pipelines, see Understanding OpenShift Pipelines.

Compatibility and support matrix

Some features in this release are currently in Technology Preview. These experimental features are not intended for production use.

In the table, features are marked with the following statuses:

TP

Technology Preview

GA

General Availability

Table 1. Compatibility and support matrix
Red Hat OpenShift Pipelines Version Component Version OpenShift Version Support Status

Operator

Pipelines

Triggers

CLI

Catalog

Chains

Hub

Pipelines as Code

1.9

0.41.x

0.22.x

0.28.x

NA

0.13.x (TP)

1.11.x

0.15.x (GA)

4.11, 4.12, 4.13 (planned)

GA

1.8

0.37.x

0.20.x

0.24.x

NA

0.9.0 (TP)

1.8.x (TP)

0.10.x (TP)

4.10, 4.11, 4.12 (planned)

GA

1.7

0.33.x

0.19.x

0.23.x

0.33

0.8.0 (TP)

1.7.0 (TP)

0.5.4 (TP)

4.9, 4.10

GA

1.6

0.28.x

0.16.x

0.21.x

0.28

N/A

N/A

N/A

4.9

GA

1.5

0.24.x

0.14.x (TP)

0.19.x

0.24

N/A

N/A

N/A

4.8

GA

1.4

0.22.x

0.12.x (TP)

0.17.x

0.22

N/A

N/A

N/A

4.7

GA

Additionally, support for running Red Hat OpenShift Pipelines on ARM hardware is in Technology Preview.

For questions and feedback, you can send an email to the product team at pipelines-interest@redhat.com.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.

Release notes for Red Hat OpenShift Pipelines General Availability 1.9

With this update, Red Hat OpenShift Pipelines General Availability (GA) 1.9 is available on OpenShift Container Platform 4.11 and later versions.

New features

In addition to the fixes and stability improvements, the following sections highlight what is new in Red Hat OpenShift Pipelines 1.9.

Pipelines

  • With this update, you can specify pipeline parameters and results in arrays and object dictionary forms.

  • This update provides support for Container Storage Interface (CSI) and projected volumes for your workspace.

  • With this update, you can specify the stdoutConfig and stderrConfig parameters when defining pipeline steps. Defining these parameters helps to capture standard output and standard error, associated with steps, to local files.

  • With this update, you can add variables in the steps[].onError event handler, for example, $(params.CONTINUE).

  • With this update, you can use the output from the finally task in the PipelineResults definition. For example, $(finally.<pipelinetask-name>.result.<result-name>), where <pipelinetask-name> denotes the pipeline task name and <result-name> denotes the result name.

  • This update supports task-level resource requirements for a task run.

  • With this update, you do not need to recreate parameters that are shared, based on their names, between a pipeline and the defined tasks. This update is part of a developer preview feature.

  • This update adds support for remote resolution, such as built-in git, cluster, bundle, and hub resolvers.

Triggers

  • This update adds the Interceptor CRD to define NamespacedInterceptor. You can use NamespacedInterceptor in the kind section of interceptors reference in triggers or in the EventListener specification.

  • This update enables CloudEvents.

  • With this update, you can configure the webhook port number when defining a trigger.

  • This update supports using trigger eventID as input to TriggerBinding.

  • This update supports validation and rotation of certificates for the ClusterInterceptor server. 

    • Triggers perform certificate validation for core interceptors and rotate a new certificate to ClusterInterceptor when its certificate expires.

CLI 

  • This update supports showing annotations in the describe command.

  • This update supports showing pipeline, tasks, and timeout in the pr describe command.

  • This update adds flags to provide pipeline, tasks, and timeout in the pipeline start command.

  • This update supports showing the presence of workspace, optional or mandatory, in the describe command of a task and pipeline.

  • This update adds the timestamps flag to show logs with a timestamp.

  • This update adds a new flag --ignore-running-pipelinerun, which ignores the deletion of TaskRun associated with PipelineRun.

  • This update adds support for experimental commands. This update also adds experimental subcommands, sign and verify to the tkn CLI tool.

  • This update makes the Z shell (Zsh) completion feature usable without generating any files.

  • This update introduces a new CLI tool called opc. It is anticipated that an upcoming release will replace the tkn CLI tool with opc.

    • The new CLI tool opc is a Technology Preview feature.

    • opc will be a replacement for tkn with additional Red Hat OpenShift Pipelines specific features, which do not necessarily fit in tkn.

Operator

  • With this update, you can install Pipelines as Code as a separate component, not as a part of TektonAddon. You can configure Pipelines as Code in the TektonConfig CRD.

  • With this update, you can also modify Pipelines as Code configurations in the TektonConfig CRD.

  • With this update, if you disable the developer perspective, the Operator does not install developer console related custom resources.

  • This update includes ClusterTriggerBinding support for Bitbucket Server and Bitbucket Cloud and helps you to reuse a TriggerBinding across your entire cluster.

Resolvers

Resolvers is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/.

  • With this update, you can configure pipeline resolvers in the TektonConfig CRD. You can enable or disable these pipeline resolvers:  enable-bundles-resolver, enable-cluster-resolver, enable-git-resolver, and enable-hub-resolver.

    apiVersion: operator.tekton.dev/v1alpha1
    kind: TektonConfig
    metadata:
      name: config
    spec:
      pipeline:
        enable-bundles-resolver: true
        enable-cluster-resolver: true
        enable-git-resolver: true
        enable-hub-resolver: true
    ...

    You can also provide resolver specific configurations in TektonConfig. For example, you can define the following fields in the map[string]string format to set configurations for individual resolvers:

    apiVersion: operator.tekton.dev/v1alpha1
    kind: TektonConfig
    metadata:
      name: config
    spec:
      pipeline:
        bundles-resolver-config:
          default-service-account