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 OpenShift Pipelines, see Understanding OpenShift Pipelines.
OpenShift Pipelines Technology Preview (TP) 1.0 is now available on OpenShift Container Platform 4.4. OpenShift Pipelines TP 1.0 is updated to support:
Tekton Pipelines 0.11.3
tkn CLI 0.9.0
Tekton Triggers 0.4.0
ClusterTasks based on Tekton Catalog 0.11
In addition to the fixes and stability improvements, here is a highlight of what’s new in OpenShift Pipelines 1.0.
Support for v1beta1 API Version.
Support for an improved LimitRange. Previously, LimitRange was specified exclusively for the TaskRun and the PipelineRun. Now there is no need to explicitly specify the LimitRange. The minimum LimitRange across the namespace is used.
Support for sharing data between Tasks using TaskResults and TaskParams.
Pipelines can now be configured to not overwrite the
HOME environment variable and
workingDir of Steps.
Similar to Task Steps,
sidecars now support script mode.
You can now specify a different scheduler name in TaskRun
Support for variable substitution using Star Array Notation.
Tekton Controller can now be configured to monitor an individual namespace.
A new description field is now added to the specification of Pipeline, Task, ClusterTask, Resource, and Condition.
Addition of proxy parameters to Git PipelineResources.
describe subcommand is now added for the following
Support added for
v1beta1 to the following commands along with backward comptibility for
The following commands can now list output from all namespaces using the
--all-namespaces flag option:
tkn task list
tkn pipeline list
tkn taskrun list
tkn pipelinerun list
The output of these commands is also enhanced to display information without headers using the
--no-headers flag option.
You can now start a Pipeline using default parameter values by specifying
--use-param-defaults flag in the
tkn pipelines start command.
Support for Workspace is now added to
tkn pipeline start and
tkn task start commands.
clustertriggerbinding command is now added with the following subcommands:
You can now directly start a pipeline run using a local or remote
describe subcommand now displays an enhanced and detailed output. With the addition of new fields, such as
param description, and
sidecar status, the command output now provides more detailed information about a specific
tkn task log command now displays logs directly if only one task is present in the namespace.
Triggers can now create both
v1beta1 Pipeline resources.
Support for new Common Expression Language (CEL) interceptor function -
compareSecret. This function securely compares strings to secrets in CEL expressions.
Support for authentication and authorization at the EventListener Trigger level.
The following items are deprecated in this release:
The environment variable
$HOME, and variable
workingDir in the Steps specification are deprecated and might be changed in a future release. Currently in a Step container,
workingDir are overwritten to
In a later release, these two fields will not be modified, and will be set to values defined in the container image and Task YAML.
For this release, use flags
disable-working-directory-overwrite to disable overwriting of the
The following commands are deprecated and might be removed in the future release:
tkn pipeline create
tkn task create
-f flag with the
tkn resource create command is now deprecated. It might be removed in the future release.
-t flag and the
--timeout flag (with seconds format) for the
tkn clustertask create command are now deprecated. Only duration timeout format is now supported, for example
1h30s. These deprecated flags might be removed in the future release.
If you are upgrading from an older version of OpenShift Pipelines, you must delete your existing deployments before upgrading to OpenShift Pipelines version 1.0. To delete an existing deployment, you must first delete Custom Resources and then uninstall the OpenShift Pipelines Operator. For more details, see the uninstalling OpenShift Pipelines section.
Submitting the same
v1alpha1 Tasks more than once results in an error. Use
oc replace instead of
oc apply when re-submitting a
DeploymentConfig Task triggered a new deployment build even when an image build was already in progress. This caused the deployment of the Pipeline to fail. With this fix, the
deploy task command is now replaced with the
oc rollout status command which waits for the in-progress deployment to finish.
APP_NAME parameter is now added in Pipeline templates.
Previously, the Pipeline template for Java S2I failed to look up the image in the registry. With this fix, the image is looked up using the existing image PipelineResources instead of the user provided
All the Openshift Pipelines images are now based on the Red Hat Universal Base Images (UBI).
Previously, when the Pipeline was installed in a namespace other than
tkn version command displayed the Pipeline version as
unknown. With this fix, the
tkn version command now displays the correct Pipeline version in any namespace.
-c flag is no longer supported for the
tkn version command.
Non-admin users can now list the ClusterTriggerBindings.
The EventListener CompareSecret function is now fixed for the CEL Interceptor.
start subcommands for
clustertask now correctly display the output in case a Task and ClusterTask have the same name.
Previously, the OpenShift Pipelines Operator modified the privileged Security Context Constraints (SCCs), which caused an error during cluster upgrade. This error is now fixed.
tekton-pipelines namespace, the timeouts of all TaskRuns and PipelineRuns are now set to the value of
default-timeout-minutes field using the ConfigMap.
Previously, the Pipelines section in the web console was not displayed for non-admin users. This issue is now resolved.