Skip to content

Commit 76ea4e5

Browse files
pneedle-rhpneedle-rh
authored
Merge pull request #45306 from pneedle-rh/osdocs-3454-adding-rosa-ui-cluster-creation-procedures
OSDOCS-3454 - Adding ROSA UI cluster creation procedures
2 parents 4c3b290 + 2dc16c3 commit 76ea4e5

17 files changed

+873
-113
lines changed

‎_topic_maps/_topic_map_rosa.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -123,7 +123,7 @@ Name: Installing, accessing, and deleting ROSA clusters
123123
Dir: rosa_install_access_delete_clusters
124124
Distros: openshift-rosa
125125
Topics:
126-
- Name: Creating a ROSA cluster with STS quickly
126+
- Name: Creating a ROSA cluster with STS using the default options
127127
File: rosa-sts-creating-a-cluster-quickly
128128
- Name: Creating a ROSA cluster with STS using customizations
129129
File: rosa-sts-creating-a-cluster-with-customizations

‎modules/rosa-creating-operator-roles-and-oidc-manually-ocm.adoc

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * rosa_getting_started_sts/rosa_creating_a_cluster_with_sts/rosa-sts-creating-a-cluster-with-customizations.adoc
4+
5+
:_content-type: CONCEPT
6+
[id="rosa-creating-operator-roles-and-oidc-manually-ocm_{context}"]
7+
= Creating the Operator roles and OIDC provider using {cluster-manager}
8+
9+
If you use {cluster-manager-first} to install your cluster and opt to create the required AWS IAM Operator roles and the OIDC provider using `manual` mode, you are prompted to select one of the following methods to install the resources. The options are provided to enable you to choose a resource creation method that suits the needs of your organization:
10+
11+
//CloudFormation:: You can use this method to create the Operator roles and the OIDC provider from the CLI using an AWS CloudFormation template and a parameter file. For more information about AWS CloudFormation, see the link:https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html[AWS documentation].
12+
13+
AWS CLI (`aws`):: With this method, you can download and extract an archive file that contains the `aws` commands and policy files required to create the IAM resources. Run the provided CLI commands from the directory that contains the policy files to create the Operator roles and the OIDC provider.
14+
15+
ROSA CLI (`rosa`):: You can run the commands provided by this method to create the Operator roles and the OIDC provider for your cluster using `rosa`.
16+
17+
If you use `auto` mode, {cluster-manager} creates the Operator roles and the OIDC provider automatically, using the permissions provided through the {cluster-manager} IAM role. To use this feature, you must apply admin privileges to the role.

‎modules/rosa-sts-about-operator-role-prefixes.adoc

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * rosa_getting_started/rosa-sts-about-iam-resources.adoc
4+
5+
:_content-type: CONCEPT
6+
[id="rosa-sts-about-operator-role-prefixes_{context}"]
7+
= About custom Operator IAM role prefixes
8+
9+
Each {product-title} (ROSA) cluster that uses the AWS Security Token Service (STS) requires cluster-specific Operator IAM roles.
10+
11+
By default, the Operator role names are prefixed with the cluster name and a random 4-digit hash. For example, the Cloud Credential Operator IAM role for a cluster named `mycluster` has the default name `mycluster-<hash>-openshift-cloud-credential-operator-cloud-credentials`, where `<hash>` is a random 4-digit string.
12+
13+
This default naming convention enables you to easily identify the Operator IAM roles for a cluster in your AWS account.
14+
15+
When you create the Operator roles for a cluster, you can optionally specify a custom prefix to use instead of `<cluster_name>-<hash>`. By using a custom prefix, you can prepend logical identifiers to your Operator role names to meet the requirements of your environment. For example, you might prefix the cluster name and the environment type, such as `mycluster-dev`. In that example, the Cloud Credential Operator role name with the custom prefix is `mycluster-dev-openshift-cloud-credential-operator-cloud-credenti`.
16+
17+
[NOTE]
18+
====
19+
The role names are truncated to 64 characters.
20+
====

‎modules/rosa-sts-creating-a-cluster-quickly-cli.adoc

Lines changed: 79 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,79 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * rosa_getting_started_sts/rosa_creating_a_cluster_with_sts/rosa-sts-creating-a-cluster-quickly.adoc
4+
// * rosa_getting_started/rosa-getting-started.adoc
5+
6+
:_content-type: PROCEDURE
7+
[id="rosa-sts-creating-cluster-using-defaults-cli_{context}"]
8+
= Creating a cluster with the default options using the CLI
9+
10+
When using the {product-title} (ROSA) CLI (`rosa`) to create a cluster that uses the AWS Security Token Service (STS), you can select the default options to create the cluster quickly.
11+
12+
.Prerequisites
13+
14+
* You have completed the AWS prerequisites for ROSA with STS.
15+
* You have available AWS service quotas.
16+
* You have enabled the ROSA service in the AWS Console.
17+
* You have installed and configured the latest ROSA CLI (`rosa`) on your installation host.
18+
+
19+
[NOTE]
20+
====
21+
To successfully install ROSA 4.10 clusters, use the latest version of the ROSA CLI.
22+
====
23+
* You have logged in to your Red Hat account by using the `rosa` CLI.
24+
* You have verified that the AWS Elastic Load Balancing (ELB) service role exists in your AWS account.
25+
26+
.Procedure
27+
28+
. Create the required account-wide roles and policies, including the Operator policies:
29+
+
30+
[source,terminal]
31+
----
32+
$ rosa create account-roles --mode auto
33+
----
34+
+
35+
[NOTE]
36+
====
37+
When using `auto` mode, you can optionally specify the `-y` argument to bypass the interactive prompts and automatically confirm operations.
38+
====
39+
40+
. Create a cluster with STS using the defaults. When you use the defaults, the latest stable OpenShift version is installed:
41+
+
42+
[source,terminal]
43+
----
44+
$ rosa create cluster --cluster-name <cluster_name> --sts --mode auto <1>
45+
----
46+
<1> Replace `<cluster_name>` with the name of your cluster.
47+
+
48+
[NOTE]
49+
====
50+
When you specify `--mode auto`, the `rosa create cluster` command creates the cluster-specific Operator IAM roles and the OIDC provider automatically. The Operators use the OIDC provider to authenticate.
51+
====
52+
53+
. Check the status of your cluster:
54+
+
55+
[source,terminal]
56+
----
57+
$ rosa describe cluster --cluster <cluster_name|cluster_id>
58+
----
59+
+
60+
The following `State` field changes are listed in the output as the cluster installation progresses:
61+
+
62+
* `waiting (Waiting for OIDC configuration)`
63+
* `pending (Preparing account)`
64+
* `installing (DNS setup in progress)`
65+
* `installing`
66+
* `ready`
67+
+
68+
[NOTE]
69+
====
70+
If the installation fails or the `State` field does not change to `ready` after about 40 minutes, check the installation troubleshooting documentation for details. For more information, see _Troubleshooting installations_. For steps to contact Red Hat Support for assistance, see _Getting support for Red Hat OpenShift Service on AWS_.
71+
====
72+
73+
. Track the progress of the cluster creation by watching the OpenShift installer logs:
74+
+
75+
[source,terminal]
76+
----
77+
$ rosa logs install --cluster <cluster_name|cluster_id> --watch <1>
78+
----
79+
<1> Specify the `--watch` flag to watch for new log messages as the installation progresses. This argument is optional.

0 commit comments

Comments
 (0)