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.2 | 0.13.0 (GA) | 0.13.0 (GA) | 1.14, 1.15, and 1.16 | 4.12, 4.13, 4.14, 4.15, 4.16, and 4.17 | GA |
| 1.1 | 0.13.0 (GA) | 0.13.0 (GA) | 1.13, 1.14, and 1.15 | 4.12, 4.13, 4.14, 4.15, and 4.16 | GA |
| 1.0 | 0.12.0 (GA) | 0.12.0 (GA) | 1.12, 1.13, 1.14, and 1.15 | 4.12, 4.13, 4.14, 4.15, and 4.16 | GA |
1.2. 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.
1.3. Release notes for Builds General Availability 1.2
Builds General Availability (GA) 1.2 is now available on OpenShift Container Platform 4.12 and later versions.
1.3.1. New features
The following section highlights what is new in Builds 1.2.
1.3.1.1. Builds
With this update, you can use the builds for Red Hat OpenShift on an OpenShift Container Platform cluster that runs on the ARM, IBM Power, or IBM Z platforms. The components to build images with Shipwright and Shared Resource CSI Driver are available.
ImportantBuilds for ARM, IBM Power, and IBM Z clusters 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 Technology Preview Features Support Scope.
- With this update, you can deploy Builds on the clusters that are configured to run behind a network proxy.
- With this update, you can deploy Builds on the clusters that run in a disconnected network environment.
-
With this update, you can use the
buildahandsource-to-imagebuild strategies to mount a Red Hat subscription entitlement key from any supported volume source. This is useful when you need builds to install Red Hat subscription content by usingyumordnfcommands. -
With this update, you can create a Shipwright
Buildobject by using thebuildahorsource-to-imagebuild strategies from the examples provided in the Developer perspective of the OpenShift Container Platform web console. You can change the parameters in these examples to create customBuildobjects. With this update, you can download the binaries for the
shpCLI from the Developer perspective of the OpenShift Container Platform web console. The CLI is available for the following operating systems and architectures:Operating system Architecture Linux
amd64
Windows
amd64
Darwin
amd64 (macOS Intel)
1.3.2. Fixed issues
The following section highlights fixed issues in Builds 1.2.
-
Before this update, the Shared Resource CSI Driver was unable to mount
SharedSecretandSharedConfigMapresources due to missing OpenShift RBAC permissions. With this update, the global permissions are granted to the Shared Resources CSI driver. Now, the Shared Resource CSI Driver can accessSharedSecretandSharedConfigMapresources and perform the required permission checks without any additional action from the cluster administrators.
1.3.3. Known issues
The following section highlights known issues in Builds 1.2.
The default build strategies fail on clusters with ARM, IBM Power, or IBM Z worker node CPU architectures.
As a workaround, perform the following steps:
Download the following multi variant of the default
ClusterBuildStrategyresources to your cluster:-
buildah-multi: buildah-multi.yaml(Internal Red Hat site download link) -
source-to-image-multi: source_to_image_multi.yaml(Internal Red Hat site download link)
-
Update your
Buildresource to use the corresponding build strategy by running one of the following commands:Buildah
$ oc apply -f buildah-multi.yaml
Source-to-image
$ oc apply -f source_to_image_multi.yaml
-
The default
buildahClusterBuildStrategyfails if the output image is not defined byBuildorBuildRunresource. As a workaround, define the output image URL. The URL can also be the path to the internal registry.
