Release Notes

Workload Availability for Red Hat OpenShift 23.2

Workload Availability release notes

Red Hat Customer Content Services

Abstract

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

Preface

Providing feedback on Workload Availability for Red Hat OpenShift documentation

We appreciate your feedback on our documentation. Let us know how we can improve it. To do so:

  1. Go to the JIRA website.
  2. Enter a descriptive title in the Summary field.
  3. Enter your suggestion for improvement in the Description field. Include links to the relevant parts of the documentation.
  4. Enter your username in the Reporter field.
  5. Enter the affected versions in the Affects Version/s field.
  6. Click Create at the bottom of the dialog.

Chapter 1. Workload Availability for Red Hat OpenShift 23.2 release notes

Workload Availability for Red Hat OpenShift version 23.2 is now available.

1.1. New features and enhancements

This release adds improvements related to the following components and concepts.

  • Node Health Check operator enhancements introduced in Workload Availability for Red Hat OpenShift version 23.2:

    • escalatingRemediations support. Previously, the Node Health Check Operator supported only one remediation per configuration. With this release, multiple remediations per configuration are supported. Multiple remediations are sequenced, and executed one after another until remediation succeeds.
    • Metal3 remediation support. Previously, the only remediation provider available for Node Health Check was Self Node Remediation. With this release, the new Metal3 remediation provider is also supported. Metal3 remediation is available for OpenShift Container Platform version 4.13 and later versions.
    • User-specific Custom Resource (CR). Previously, the default Node Health Check CR was created automatically during installation. With this release, the Node Health Check Operator does not have a default CR. Instead, the user must create a CR corresponding to their requirements.

For more information on these enhancements, see the Node Health Check section of the Workload Availability for Red Hat OpenShift documentation.

1.2. Deprecated and removed features

No features were deprecated and/or removed in this release.

1.3. Bug fixes

No notable bugs were fixed in this release.

1.4. Technology preview features

There are no new technology preview features in this release.

1.5. Known issues

No known issues were identified in this release.

Legal Notice

Copyright © 2024 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat 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 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.