Release notes
Highlights of what is new and what has changed with this OpenShift Builds release
Abstract
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.3 | 0.14.0 (GA) | 0.14.0 (GA) | 1.14, 1.15, 1.16, 1.17 | 4.14, 4.15, 4.16, 4.17 | GA |
| 1.2 | 0.13.0 (GA) | 0.13.0 (GA) | 1.14, 1.15, 1.16 | 4.12, 4.13, 4.14, 4.15, 4.16, 4.17 | 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.3
With this update, Builds 1.3 is now Generally Available (GA) on OpenShift Container Platform 4.14, 4.15, 4.16, and 4.17.
1.3.1. New features
The following section highlights what is new in Builds 1.3.
- With this update, the Builds for Red Hat OpenShift Operator deploys Shipwright v0.14 APIs, controllers, and webhook.
-
With this update, while creating the
BuildorBuildRunresources with OpenShift Builds Client, you can set the parameters by using the--param-valueflag.
1.3.2. Fixed issues
The following section highlights fixed issues in Builds 1.3.
-
Before this update, when you installed Builds without installing OpenShift Pipelines, the Builds attempted to deploy OpenShift Pipelines and enable Pipelines controllers. Builds incorrectly configured OpenShift Pipelines and failed to deploy the controllers. With this update, Builds creates a valid
TektonConfigcustom resource and correctly deploys the Pipelines controllers. -
Before this update, when you tried to run builds using builds for Red Hat OpenShift installed on ARM64, IBM Power®, or IBM Z® worker node CPU architectures, the build would fail because images were based on AMD64 platform only. Now, the AMD64 images are replaced with a
multi-archimage inbuildahandsource-to-imagebuild strategies, therefore you can run builds on all the architectures. -
Before this update, when you enabled cluster monitoring in the
openshift-buildsnamespace, theTargetDownalert was received on the Shared Resources Container Storage Interface (CSI) DriverServiceMonitorresource due to an incorrect server name address. With this update, the server name is updated to the correct address in the Shared Resources CSI DriverServiceMonitorresource and theTargetDownalert is no longer triggered. -
Before this update, the Operator logo was not displayed in the OperatorHub. To display the Operator logo in the OperatorHub, you had to update the logo in the File Based Catalog (FBC) catalog format even after specifying it in the CSV file. With this update, the Operator logo data is specified in the catalog
config.yamlfiles and the logo is displayed in the OperatorHub.
1.3.3. Deprecated features
The following section highlights deprecated features in Builds 1.3.
With this update, the following channels are deprecated and are planned to be removed in a future release:
-
stable-v1 -
openshift-builds-1.0
Instead, use the
builds-1.3channel.-
Legal Notice
Copyright © 2024 Red Hat, Inc.
OpenShift documentation is licensed under the Apache License 2.0 (https://www.apache.org/licenses/LICENSE-2.0).
Modified versions must remove all Red Hat trademarks.
Portions adapted from https://github.com/kubernetes-incubator/service-catalog/ with modifications by Red Hat.
Red Hat, Red Hat Enterprise Linux, the Red Hat logo, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation’s permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.
