SupportConsoleDevelopersStart a trialContact

Release notes

builds for Red Hat OpenShift 1.2

Highlights of what is new and what has changed with this OpenShift Builds release

Red Hat OpenShift Documentation Team

Abstract

The release notes for OpenShift Builds summarize all new features and enhancements, notable technical changes, major corrections from the previous version, and any known bugs upon general availability.

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 VersionComponent VersionCompatible Openshift Pipelines VersionOpenShift VersionSupport

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.

    Important

    Builds 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 buildah and source-to-image build 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 using yum or dnf commands.
  • With this update, you can create a Shipwright Build object by using the buildah or source-to-image build 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 custom Build objects.

  • With this update, you can download the binaries for the shp CLI from the Developer perspective of the OpenShift Container Platform web console. The CLI is available for the following operating systems and architectures:

    Operating systemArchitecture

    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 SharedSecret and SharedConfigMap resources 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 access SharedSecret and SharedConfigMap resources 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:

    1. Download the following multi variant of the default ClusterBuildStrategy resources to your cluster:

    2. Update your Build resource 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 buildah ClusterBuildStrategy fails if the output image is not defined by Build or BuildRun resource. As a workaround, define the output image URL. The URL can also be the path to the internal registry.

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.

Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.