Chapter 1. Workload Availability for Red Hat OpenShift 25.1 release notes
Chapter 1. Workload Availability for Red Hat OpenShift 25.1 release notes Workload Availability for Red Hat OpenShift version 25.1 is now available. 1.1. New features and enhancements This release adds improvements related to the following components and concepts: Starting with version 25.1, Workload Availability for Red Hat OpenShift is designed for Federal Information Processing Standards (FIPS) compliance. 1.2. Deprecated and removed features Starting with version 25.1, the Self Node Remediation (SNR) Operator is not installed automatically with the Node Health Check (NHC) Operator. You can choose to install a remediation provider according to your requirements. It is recommended that you install either the Self Node Remediation (SNR) Operator, or the Fence Agent Remediation (FAR) Operator, or the Machine Deletion Remediation (MDR) Operator. Some FAR agents are removed from the list of supported agents. For an updated list of the agents that are currently supported by the FAR Operator, see Agents supported by the FAR Operator . 1.3. Bug fixes While using an AWS cluster, the NodeHeathCheck page is unavailable under the Compute menu on the Red Hat OpenShift web console. ( ECOPROJECT-1469 ) Cause: Certain requirements for the NodeHealthCheck Custom Resource Definition (CRD) might cause this issue. Consequence: The NodeHeathCheck page was disabled due to requirements that were not met by the NHC CRD. Fix: NodeHealthCheck CRD requirement is now removed. Result: The NodeHeathCheck page is available under the Compute menu on the Red Hat OpenShift web console. The Node selection on the Node Health Check page is not displayed correctly in the Role column. ( ECOPROJECT-2326 ) Cause: The Node Health Check page does not filter out any label that is longer than 24 characters. Consequence: The page considered any label that was longer than 24 characters to be a label that represents the node role. The label would then show up in the Role column of Node selection table. Fix: Detect the labels on the node role by checking if label is prefixed by node-role.kubernetes.io/ label. Result: The Role column of Node selection table shows node roles correctly. The Self Node Remediation (SNR) CR is not removed when a node is deleted by the Machine Deletion Remediation on escalating remediation. ( ECOPROJECT-2489 ) Cause : Node Health Check does not remove orphaned CRs for deleted nodes and SNR does not allow the removal of orphaned remediations. This might occur on escalating remediation, where SNR starts and fails in the allocated time, then MDR is triggered and remediates by deleting the node. Consequence : SNR remediation which belongs to the deleted node is not removed. Fix : NHC triggers CR deletion when the node is deleted. When SNR detects a deleted remediation and NHC marks it as a timeout, then SNR allows the removal of this orphaned remediation. Result: NHC deletes orphaned CRs for deleted nodes, while SNR removes these CRs when it detects a deleted remediation that is marked timeout by NHC. 1.4. Technology Preview features There are no new Technology Preview features in this release. 1.5. Known issues The fence agent, in the Fence Agents Remediation Operator pod, needs network connectivity to the management interface of the unhealthy node. On some platforms, such as IBM, the pod network lacks this network connectivity. 1.6. Mapping the Workload Availability for Red Hat OpenShift release to the Operator releases The RHWA version numbers are based on the year and the iteration in that year. For example, 25.1 is the first release in 2025. The Operator version numbers follow semantic versioning. Table 1.1. Release Mapping Workload Availability Version Operator Version 25.1 Self Node Remediation (SNR) Operator 0.10.0 Fence Agents Remediation (FAR) Operator 0.5.0 Machine Deletion Remediation (MDR) Operator 0.4.0 Node Health Check (NHC) Operator 0.9.0 Node Maintenance Operator (NMO) 5.4.0