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. Table 1.1. Compatibility and support matrix Builds Version Component Version Compatible Openshift Pipelines Version OpenShift Version Support Operator Builds (Shipwright) CLI 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.1.1 With this update, Builds 1.1.1 is now Generally Available (GA) on OpenShift Container Platform 4.12, 4.13, 4.14, 4.15, and 4.16. 1.3.1. Fixed issues The following section highlights fixed issues in Builds 1.1.1. With this update, the Shared Resource Container Storage Interface (CSI) Driver has the following permissions: Create subject access reviews Get, list, and watch Shared Resource objects 1.4. Release notes for Builds General Availability 1.1 With this update, Builds 1.1 is now Generally Available (GA) on OpenShift Container Platform 4.12, 4.13, 4.14, 4.15, and 4.16. 1.4.1. New features The following sections highlight what is new in Builds 1.1. 1.4.1.1. Builds The builds controllers now use Tekton's V1 API to create and access the TaskRun that backs a BuildRun . With this release, you can now define a build without any source. This is useful if you want to run the build using only the local source. The output image section now supports an optional timestamp field to change the image creation timestamp. Use the SourceTimestamp string to set it to match the source timestamp. With this release, the .source.type field is now required in both build and buildRun . With this release, the Operator now installs Shipwright by default and introduces several user experience enhancements for Builds. 1.4.1.2. Shared Resource CSI Driver The Shared Resource CSI Driver is now generally available. With this release, the CSI Shared Driver enables sharing of ConfigMaps and secrets across different namespaces in Kubernetes clusters. The driver has permission to read all Kubernetes secrets. This feature improves resource efficiency by reducing duplication and simplifies configuration management in multi-tenant environments. Administrators can define access policies to control which namespaces can read or modify these shared resources. 1.4.2. Known issues The following section highlights known issues in Builds 1.1. 1.4.2.1. Builds With this release, direct upgrades from Builds 1.0 to Builds 1.1 are not supported. To upgrade to Builds 1.1, you must delete the ShipwrightBuild object, uninstall the Builds 1.0.z operator, and then install the Builds 1.1.0 operator from OperatorHub.

Commands: