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

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

1.1. New features and enhancements

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

Workload Availability for Red Hat OpenShift now includes data analysis which enhances observability for the workload availability Operators. The data provides metrics about the activity of the remediation Operators and the effect on the cluster. These metrics improve decision-making capabilities, enable data-driven optimization, and enhance overall system performance.
- For more information on these metrics, see the About metrics for the workload availability Operators section of the Workload Availability for Red Hat OpenShift documentation.
The Fence Agents Remediation (FAR) Operator now includes:
- Support for non-graceful node shutdown. The configurable remediationStrategy parameter includes an 'OutOfServiceTaint' setting that represents a non-graceful node shutdown. A non-graceful node shutdown occurs when a node is shut down and not detected, instead of triggering an in-operating system shutdown.
  - For more information on the remediationStrategy parameter, see the Understanding the Fence Agents Remediation Template configuration section of the documentation.
- A list of the agents currently supported by the FAR Operator.
  - For more information on the list of agents, see the Agents supported by the Fence Agents Remediation Operator section of the documentation.

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

Node Health Check (NHC) is unable to use two remediation templates of the same remediator. (ECOPROJECT-1229)
- Cause: NHC operator cannot use multiple remediation templates of the same kind.
- Consequence: NHC escalation remediation feature is limited and less robust.
- Fix: NHC has added support to handle multiple remediation templates of the same kind, while keeping backward compatibility.
- Result: For remediators that support this feature, NHC can use multiple templates of the same kind when configured with escalation remediation.
When the Node Maintenance Operator (NMO) completes maintenance on a node the Node Health Check (NHC) Operator does not trigger remediation, in case the node is unhealthy. (ECOPROJECT-1988)
- Cause: NHC operator does not check the health status of a node that has completed maintenance.
- Consequence: Remediation is not triggered on the node after the node has completed maintenance.
- Fix: Previously, a regression issue was introduced in NHC 0.8.0 that caused the Operator to not check the health status of a node that has completed maintenance. In this release, the regression issue is fixed with an updated version of the Operator, NHC 0.8.1.
- Result: As expected, the NHC operator now triggers remediation on an unhealthy node that has completed maintenance.

There are no new Technology preview features in this release.

No known issues were identified in this release.