You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To use the latest version of the ROSA CLI tool, download the ROSA CLI tool from the Hybrid Cloud Console. If you already have this tool, the procedure is the same for updates.
11
+
12
+
.Procedure
13
+
14
+
. Download the file from the link:https://console.redhat.com/openshift/downloads[Hybrid Cloud Console].
15
+
16
+
. Unzip the downloaded file.
17
+
18
+
. Move the file to the `/usr/bin/rosa` directory by running the following command:
19
+
+
20
+
[source,terminal]
21
+
----
22
+
$ sudo mv rosa /usr/bin/rosa
23
+
----
24
+
25
+
. Confirm your version by running the following command:
26
+
+
27
+
[source,terminal]
28
+
----
29
+
$ rosa version
30
+
----
31
+
+
32
+
.Example output
33
+
34
+
[source,terminal]
35
+
----
36
+
<version>
37
+
Your ROSA CLI is up to date.
38
+
----
39
+
40
+
//Potential step 4: In the terminal, type `chmod a+x /usr/bin/rosa` to make the ROSA binary you downloaded executable.
{product-title} (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.
10
10
11
-
[id="about-this-release-section_{context}"]
12
-
== About this release
11
+
{product-title} clusters are available on the link:https://console.redhat.com/openshift[Hybrid Cloud Console]. With the Red Hat OpenShift Cluster Manager application for ROSA, you can deploy {product-title} clusters to either on-premises or cloud environments.
13
12
14
-
{product-title} https://access.redhat.com/errata/RHEA-2022:2252[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 {product-title} 4.10 are included in this topic.
13
+
include::modules/rosa-update-cli-tool.adoc[]
15
14
16
-
{product-title} clusters are available at https://console.redhat.com/openshift. With the {cluster-manager-first} application for ROSA, you can deploy {product-title} clusters to either on-premise or cloud environments.
15
+
[id="rosa-new-changes-and-updates_{context}"]
16
+
== New changes and updates
17
17
18
-
[id="about-this-release_{context}"]
19
-
== ROSA layered and dependent component support and compatibility
20
-
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 xref:../rosa_architecture/rosa_policy_service_definition/rosa-life-cycle.adoc#rosa-life-cycle[{product-title} update life cycle].
18
+
[id="rosa-q1-2023_{context}"]
19
+
=== Q1 2023
21
20
22
-
[id="rosa-new-features_{context}"]
23
-
== New features and enhancements
21
+
* Starting with ROSA CLI version 1.2.7, all new cluster OIDC provider endpoint URLs are no longer regional. AWS CloudFront is part of this implementation to improve access speed, reduce latency, and improve resiliency. This change is only available for new clusters created with ROSA CLI 1.2.7 or later. There are no supported migration paths for existing OIDC provider configurations.
24
22
25
-
[id="rosa-product-enhancements_{context}"]
26
-
=== Product enhancements
27
23
28
-
The following list describes the key features of ROSA:
29
-
30
-
* **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.
31
-
32
-
* **Latest CLI and new Operator**: ROSA Command Line Interface (CLI) 1.1.11 was released on March 9, 2022 and enabled the creation of {product-title} 4.10 clusters. Please ensure you are always using the latest ROSA CLI for the best experience. {product-title} 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 {product-title} 4.10, or it will be a part of new cluster deployments. During an upgrade to {product-title} 4.10, you will be prompted by the ROSA CLI to add a new role and policy.
33
-
34
-
* **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 {product-title} clusters. When you run these commands, the old {product-title} clusters and their relevant STS roles and policies are updated to the latest versions.
35
-
36
-
* **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 {cluster-manager-first} UI only.
37
-
38
-
[id="rosa-documentation-enhancements_{context}"]
39
-
=== Documentation enhancements
40
-
41
-
The following list describes the key documentation features of ROSA:
42
-
43
-
* **Getting started with ROSA**: {product-title} 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 {product-title} CLI interfaces. New users can accomplish the following tasks by using the getting started guide:
44
-
** Setting up the environment
45
-
** Creating a {product-title} clusters with STS using the default options
46
-
** Creating a cluster administrator user for quick cluster access
47
-
** Configuring an identity provider and granting cluster access
48
-
** Accessing a cluster through the web console
49
-
** Deploying an application from the Developer Catalog
50
-
** Revoking administrator privileges and user access
51
-
** Deleting a {product-title} cluster and the AWS STS resources
52
-
53
-
For more information, see xref:../rosa_getting_started/rosa-getting-started.adoc#rosa-getting-started[Getting started with {product-title}].
54
-
55
-
* **Documentation restructure**: The ROSA product documentation went through two phases of restructuring focused on making the following more intuitive, clear, and findable:
56
-
** Navigation menu
57
-
** Book content
58
-
** Topic flow
59
-
60
-
In addition, redirects were put in place to help ensure a seamless navigation experience in the ROSA documentation.
61
-
62
-
[id="technical-changes_{context}"]
63
-
== Notable technical changes
64
-
{product-title} 4.10 introduces the following notable technical changes.
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.
As of the {product-title} versions 4.8.35, 4.9.26, 4.10.6, the {product-title} default per-pod PID limit is **4096**. If you want to enable this PID limit, you must upgrade your {product-title} clusters to these versions or later. {product-title} clusters with prior versions use a default PID limit of **1024**.
24
+
[id="rosa-known-issues_{context}"]
25
+
== Known issues
26
+
* The OpenShift Cluster Manager roles (`ocm-role`) and user roles (`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.
27
+
* The `htpasswd` identity provider does not function as expected in all scenarios against the `rosa create admin` function.
85
28
86
29
[id="rosa-deprecated-removed-features_{context}"]
87
30
== Deprecated and removed features
@@ -90,15 +33,3 @@ Some features available in previous releases have been deprecated or removed. De
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.
93
-
94
-
[id="rosa-bug-fixes_{context}"]
95
-
== Bug fixes
96
-
97
-
[id="rosa-known-issues_{context}"]
98
-
=== Known issues
99
-
* 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.
100
-
* 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.
101
-
102
-
[id="rosa-fixed-issues_{context}"]
103
-
=== Fixed issues
104
-
* Previously, if you selected Single-AZ mode for {product-title} 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.
// Text snippet included in the following modules:
2
+
//
3
+
// * rosa_release_notes/rosa-release-notes.adoc
4
+
5
+
:_content-type: SNIPPET
6
+
* With {product-title} <release-version>, {product-title} does <something>. This functionality offers <benefits>. For more information, see link:<link-to-relevant-docs>[Documentation].
0 commit comments