×

Red Hat OpenShift Service on AWS (ROSA) is a fully-managed, turnkey application platform that allows you to focus on delivering value to your customers by building and deploying applications. Red Hat and AWS site reliability engineering (SRE) experts manage the underlying platform so you do not have to worry about the complexity of infrastructure management. ROSA provides seamless integration with a wide range of AWS compute, database, analytics, machine learning, networking, mobile, and other services to further accelerate the building and delivering of differentiating experiences to your customers.

About this release

Red Hat OpenShift Service on AWS RHEA-2022:2252 is now available. This release uses Kubernetes 1.24 with CRI-O runtime. New features, changes, and known issues that pertain to Red Hat OpenShift Service on AWS 4.10 are included in this topic.

Red Hat OpenShift Service on AWS clusters are available at https://console.redhat.com/openshift. With the Red Hat OpenShift Cluster Manager application for ROSA, you can deploy Red Hat OpenShift Service on AWS clusters to either on-premise or cloud environments.

ROSA layered and dependent component support and compatibility

The scope of support for layered and dependent components of ROSA changes independently of the ROSA version. To determine the current support status and compatibility for an add-on, see the Red Hat OpenShift Service on AWS update life cycle.

New features and enhancements

Product enhancements

The following list describes the key features of ROSA:

  • ROSA UI wizard: The new ROSA provisioning wizard UI is now available as an AWS STS-only experience. You can access the new UI wizard at https://console.redhat.com/openshift/create/rosa/wizard.

  • Latest CLI and new Operator: ROSA Command Line Interface (CLI) 1.1.11 was released on March 9, 2022 and enabled the creation of Red Hat OpenShift Service on AWS 4.10 clusters. Please ensure you are always using the latest ROSA CLI for the best experience. Red Hat OpenShift Service on AWS 4.10 has a new Operator and cloud network configuration controller. Therefore, a new Operator role and policy will be added when you upgrade to Red Hat OpenShift Service on AWS 4.10, or it will be a part of new cluster deployments. During an upgrade to Red Hat OpenShift Service on AWS 4.10, you will be prompted by the ROSA CLI to add a new role and policy.

  • Upgrade handling: The commands rosa upgrade cluster and rosa upgrade account roles are seamless and backward compatible with all the older ROSA versions and older Red Hat OpenShift Service on AWS clusters. When you run these commands, the old Red Hat OpenShift Service on AWS clusters and their relevant STS roles and policies are updated to the latest versions.

  • New AWS roles supporting the ROSA UI: The tools to manage the ocm-role and user-role and use the ROSA provisioning UI are now available in the ROSA CLI as of version 1.2.0. The ocm-role and user-role are also instrumental in facilitating ROSA STS upgrades done from the Red Hat OpenShift Cluster Manager UI only.

Documentation enhancements

The following list describes the key documentation features of ROSA:

  • Getting started with ROSA: Red Hat OpenShift Service on AWS 4.10 now includes a getting started guide. Getting Started with ROSA defines basic terminology and provides role-based next steps for developers and administrators. The tutorials walk new users through the web console and the Red Hat OpenShift Service on AWS CLI interfaces. New users can accomplish the following tasks by using the getting started guide:

    • Setting up the environment

    • Creating a Red Hat OpenShift Service on AWS clusters with STS using the default options

    • Creating a cluster administrator user for quick cluster access

    • Configuring an identity provider and granting cluster access

    • Accessing a cluster through the web console

    • Deploying an application from the Developer Catalog

    • Revoking administrator privileges and user access

    • Deleting a Red Hat OpenShift Service on AWS cluster and the AWS STS resources

  • Documentation restructure: The ROSA product documentation went through two phases of restructuring focused on making the following more intuitive, clear, and findable:

    • Navigation menu

    • Book content

    • Topic flow

In addition, redirects were put in place to help ensure a seamless navigation experience in the ROSA documentation.

Notable technical changes

Red Hat OpenShift Service on AWS 4.10 introduces the following notable technical changes.

Encrypted ephemeral instance volumes

Clusters built in July 2022 and later use encrypted ephemeral instances as part of the pre-create cluster workflow. These clusters pass the service control policies (SCPs) that demand encrypted instance volumes only.

Throttling improvements for ROSA CLI

Delays, intervals, and timeouts were improved to reduce the possibility of requests being throttled when addressing the AWS APIs.

Addition of new commands

The following commands were added:

  • Managing a managed service or appliance: rosa create|edit managed-service --id=<service> --parameter-key <parameter value>

  • Managing Red Hat OpenShift Cluster Manager roles: rosa create|list|delete ocm-role

  • Managing Red Hat OpenShift Cluster Manager users: rosa create|list|delete user-role

Increased the default per-pod PID limit

As of the Red Hat OpenShift Service on AWS versions 4.8.35, 4.9.26, 4.10.6, the Red Hat OpenShift Service on AWS default per-pod PID limit is 4096. If you want to enable this PID limit, you must upgrade your Red Hat OpenShift Service on AWS clusters to these versions or later. Red Hat OpenShift Service on AWS clusters with prior versions use a default PID limit of 1024.

Deprecated and removed features

Some features available in previous releases have been deprecated or removed. Deprecated functionality is still included in ROSA and continues to be supported; however, it will be removed in a future release of this product and is not recommended for new deployments.

ROSA non-STS deployment mode

ROSA non-STS deployment mode is no longer the preferred method for new clusters. Instead, users must deploy ROSA with the STS mode. This deprecation is in line with our new ROSA provisioning wizard UI experience at https://console.redhat.com/openshift/create/rosa/wizard.

Bug fixes

Known issues

  • The ocm-role and user-role that are key to the ROSA provisioning wizard might get enabled accidentally in your Red Hat organization by another user. However, this behavior does not affect the usability.

  • The htpasswd identity provider does not function as expected in all scenarios against the rosa create admin function. This issue will be addressed in a newer version of the ROSA CLI in a future release.

Fixed issues

  • Previously, if you selected Single-AZ mode for Red Hat OpenShift Service on AWS clusters, you could select multiple availability zones too. This issue is now fixed and you can specify only one availability zone when you select Single-AZ mode.