Chapter 1. Release notes
Release notes contain information about new and deprecated features, breaking changes, and known issues. The following release notes apply for the most recent Builds releases on OpenShift Container Platform.
Builds is an extensible build framework based on the Shipwright project, which you can use to build container images on an OpenShift Container Platform cluster. You can build container images from source code and Dockerfiles by using image build tools, such as Source-to-Image (S2I) and Buildah
. You can create and apply build resources, view logs of build runs, and manage builds in your OpenShift Container Platform namespaces.
Builds includes the following capabilities:
- Standard Kubernetes-native API for building container images from source code and Dockerfiles
-
Support for Source-to-Image (S2I) and
Buildah
build strategies - Extensibility with your own custom build strategies
- Execution of builds from source code in a local directory
- Shipwright CLI for creating and viewing logs, and managing builds on the cluster
- Integrated user experience with the Developer perspective of the OpenShift Container Platform web console
For more information about Builds, see Overview of Builds.
1.1. Compatibility and support matrix
In the table, components are marked with the following statuses:
TP | Technology Preview |
GA | General Availability |
The Technology Preview features are experimental features and are not intended for production use.
Builds Version | Component Version | Compatible Openshift Pipelines Version | OpenShift Version | Support | |
---|---|---|---|---|---|
Operator | Builds (Shipwright) | CLI | |||
1.4 | 0.15.0 (GA) | 0.15.0 (GA) | 1.16, 1.17, 1.18 and 1.19 | 4.15, 4.16, 4.17, and 4.18 | GA |
1.3 | 0.14.0 (GA) | 0.14.0 (GA) | 1.14, 1.15, 1.16, and 1.17 | 4.14, 4.15, 4.16, and 4.17 | GA |
1.2. Release notes for Builds 1.4
Builds 1.4 is now available on OpenShift Container Platform 4.15, 4.16, 4.17, and 4.18.
1.2.1. New features
The following sections highlight what is new in Builds 1.4.
- With this update, Builds for OpenShift deploys Shipwright v0.15 components.
-
With this update, you can use the optional
spec.tolerations
value to specify the tolerations for the Builds pod. -
With this update, you can use the optional
spec.nodeSelector
value to specify which nodes Builds should run on. -
With this update, you can use the optional
spec.schedulerName
value to specify the scheduler for the Builds pod. -
With this update, the
target
flag in thebuildah
strategy is available for multi-stage builds. Use the flag to specify at which stage the build should stop. With this update, you can enable cluster monitoring during Builds for Red Hat OpenShift Operator installation:
- For GUI installation, the option to enable cluster monitoring is available at namespace selection.
For CLI installation, set the cluster-monitoring label in "openshift-builds" namespace as shown below:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow apiVersion: v1 kind: Namespace metadata: labels: openshift.io/cluster-monitoring: "true" name: openshift-builds
apiVersion: v1 kind: Namespace metadata: labels: openshift.io/cluster-monitoring: "true" name: openshift-builds
1.2.2. Fixed issues
The following list highlights fixed issues in Builds 1.4.
-
Before this update, the validating webhook for the Shared Resource CSI Driver would not deploy on Red Hat OpenShift Service on AWS (ROSA) clusters. This left the component’s deployment in a permanent
pending
state. With this change, the webhook now deploys successfully on ROSA. -
Previously, Builds for Red Hat OpenShift Operator would trigger the
PrometheusOperatorRejectedResources
alert when you enable user workload monitoring on OpenShift. With this fix, Builds for Red Hat OpenShift Operator is configured correctly and the service monitor will not be picked up by the user workload monitoring stack. - Before this update, you could not run Builds from a local source code. With this update, the issue is fixed.
1.2.3. Deprecated features
The following section highlights deprecated features in Builds 1.4.
With this update, the following channels are deprecated:
- builds-1.0
- builds-1.1
- builds-1.2
Instead, use the builds-1.4 channel.