Chapter 3. Features


3.1. New and Changed features

3.1.1. Spring Boot BOM

From Red Hat support for Spring Boot 2.7 onward, the Spring Boot BOM (Bill of Materials) to manage dependencies for Red Hat supported components is not available. You can, however, manage these components individually in an application’s pom.xml file as dependencies by specifying their groupId, artifactId, and version (GAV). For more information, see Migrating applications to Spring Boot 2.7.

3.2. New features introduced in earlier 2.x releases

3.2.1. Deploy Spring Boot applications to OpenShift using the Dekorate Maven dependency

Use the Dekorate Maven dependency to deploy your Spring Boot applications to OpenShift. The Fabric8 Maven plugin is no longer supported. For information about deploying your application to OpenShift, see Dekorate Guide for Spring Boot Developers.

3.2.2. OpenJDK11 OpenShift images support multiple architectures

OpenJ9 images for IBM Z and IBM Power Systems have been deprecated. The following OpenJDK11 image has been updated to support multiple architectures:

  • ubi8/openjdk-11

You can use the OpenJDK11 image with the following architectures:

  • x86 (x86_64)
  • s390x (IBM Z)
  • ppc64le (IBM Power Systems)

If you want to use the OpenJ9 Java Virtual Machine (JVM) with the OpenJDK11 images, see Java Change in Power and Z OpenShift Images.

3.2.3. Support for OpenJDK 8 OpenJDK 11 and OpenJDK 17 RHEL 8 Universal Base Images (UBI8)

Spring Boot 2.7 introduces support for building and deploying Spring Boot applications to OpenShift with OCI-compliant Universal Base Images for Red Hat OpenJDK 8, Red Hat OpenJDK 11, and Red Hat OpenJDK 17 on RHEL 8. The RHEL 8 OpenJDK Universal Base Images replace the RHEL 8 OpenJDK builder images supported by Red Hat for use with earlier releases of Red Hat Build of Spring Boot. The previously supported RHEL 8 OpenJDK base images are no longer supported for use with Red Hat Build of Spring Boot.

3.2.4. Spring Boot metering labels for OpenShift

You can add metering labels to your Spring Boot pods and check Red Hat subscription details with the OpenShift Metering Operator.

Note

Do not add metering labels to any pods that an operator deploys and manages.

Spring Boot should use the following metering labels:

  • com.company: Red_Hat
  • rht.prod_name: Red_Hat_Runtimes
  • rht.prod_ver: 2023-Q4
  • rht.comp: Spring_Boot
  • rht.comp_ver: 2.7.18
  • rht.subcomp: <leave_blank>
  • rht.subcomp_t: application

See Metering documentation for more information.

For more information on labels, see Understanding how to update labels on nodes.

3.3. Deprecated features

No features or functionalities are marked as deprecated in this release.

3.4. Technology Preview

3.4.1. Dekorate build hooks for deploying Spring Boot applications to OpenShift Container Platform

You can use Dekorate to configure a Source-to-image build of your application that starts automatically after you compile your application with Maven. This functionality is provided as Technology Preview in Dekorate version 1.0.0 and later. Red Hat does not provide support for using this functionality in a production environment.

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.