Skip to content

Commit 1e91138

Browse files
committed
OSDOCS-14111: Updating OCM guide
1 parent 3b84802 commit 1e91138

File tree

5 files changed

+83
-22
lines changed

5 files changed

+83
-22
lines changed

modules/ocm-accesscontrol-tab.adoc

Lines changed: 53 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,13 +8,63 @@
88

99
The **Access control** tab allows the cluster owner to set up an identity provider, grant elevated permissions, and grant roles to other users.
1010

11+
[id="ocm-accesscontrol-tab-identity-providers_{context}"]
12+
== Identity providers
13+
14+
You can create your cluster's identity provider in this section. See the _Additional resources_ for more information.
15+
16+
[id="ocm-accesscontrol-tab-cluster-roles-access_{context}"]
17+
== Cluster roles and acess
18+
19+
You can create a `dedicated-admins` role for {product-short-name} clusters or `cluster-admins` role for {product-title} clusters.
20+
21+
.Procedure
22+
. Click the **Add user** button.
23+
. Enter the ID of the user you want to grant cluster admin access.
24+
. Select the appropriate group for your user. Either `dedicated-admins` for {product-short-name} clusters, or `cluster-admins` for
25+
ifdef::openshift-rosa[]
26+
{rosa-classic-short}
27+
endif::openshift-rosa[]
28+
ifdef::openshift-rosa-hcp[]
29+
{rosa-short}
30+
endif::openshift-rosa-hcp[]
31+
clusters.
32+
33+
[id="ocm-accesscontrol-tab-ocm-roles-access_{context}"]
34+
== OCM roles and access
1135
.Prerequisites
1236

1337
* You must be the cluster owner or have the correct permissions to grant roles on the cluster.
1438

1539
.Procedure
1640

17-
. Select the **Grant role** button.
41+
. Click the **Grant role** button.
1842
. Enter the Red Hat account login for the user that you wish to grant a role on the cluster.
19-
. Select the **Grant role** button on the dialog box.
20-
. The dialog box closes, and the selected user shows the "Cluster Editor" access.
43+
. Select the role from following options:
44+
** **Cluster editor** allows users or groups to manage or configure the cluster.
45+
** **Cluster viewer** allows users or groups to view cluster details only.
46+
ifdef::openshift-rosa[]
47+
** **Cluster autoscaler editor** allows users or groups to manage and configure the cluster autoscaler settings.
48+
endif::openshift-rosa[]
49+
** **Identity provider editor** allows users or groups to manage and configure the identity providers.
50+
** **Machine pool editor** allows users or groups to manage and configure the machine pools.
51+
. Click the **Grant role** button on the dialog box.
52+
53+
ifdef::openshift-rosa[]
54+
[id="ocm-accesscontrol-tab-transfer-ownership_{context}"]
55+
== Transfer ownership
56+
57+
You can transfer your cluster to another user.
58+
59+
[NOTE]
60+
====
61+
Once you transfer cluster ownership, you lose access to the cluster.
62+
====
63+
64+
.Procedure
65+
66+
. Select **Initiate transfer**.
67+
. Enter the user name, account ID, and organization ID of the user that you are transferring the cluster to.
68+
. Select **Initiate transfer**.
69+
70+
endif::openshift-rosa[]

modules/ocm-accessing.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ You can access {cluster-manager} with your configured OpenShift account.
1111
.Prerequisites
1212

1313
* You have an account that is part of an OpenShift organization.
14-
* If you are creating a cluster, your organization has specified quota.
14+
* If you are creating a cluster, your organization has a specified quota.
1515
1616
.Procedure
1717

modules/ocm-overview-tab.adoc

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,12 +10,17 @@ The **Overview** tab provides information about how the cluster was configured:
1010

1111
* **Cluster ID** is the unique identification for the created cluster. This ID can be used when issuing commands to the cluster from the command line.
1212
* **Domain prefix** is the prefix that is used throughout the cluster. The default value is the cluster's name.
13-
* **Type** shows the OpenShift version that the cluster is using.
13+
* **Type** shows the type of cluster, for example {rosa-classic-short}, {rosa-short}, or Dedicated.
1414
ifndef::openshift-rosa[]
1515
* **Control plane type** is the architecture type of the cluster. The field only displays if the cluster uses a hosted control plane architecture.
1616
endif::openshift-rosa[]
1717
* **Region** is the server region.
18+
ifdef::openshift-rosa[]
1819
* **Availability** shows which type of availability zone that the cluster uses, either single or multizone.
20+
endif::openshift-rosa[]
21+
ifdef::openshift-rosa-hcp[]
22+
* **Availability** shows multizone for {rosa-short} clusters.
23+
endif::openshift-rosa-hcp[]
1924
* **Version** is the OpenShift version that is installed on the cluster. If there is an update available, you can update from this field.
2025
* **Created at** shows the date and time that the cluster was created.
2126
* **Owner** identifies who created the cluster and has owner rights.
@@ -30,7 +35,7 @@ endif::openshift-rosa[]
3035
* **Total memory** shows the total available memory for this cluster.
3136
* **Infrastructure AWS account** displays the AWS account that is responsible for cluster creation and maintenance.
3237
ifdef::openshift-rosa-hcp[]
33-
* **Billing marketplace account** displays the AWS account that is used for billing purposes.
38+
* **Billing marketplace account** displays the AWS account that is used for billing purposes. Click on the pencil icon to edit this field.
3439
endif::openshift-rosa-hcp[]
3540
ifdef::openshift-rosa[]
3641
* **Additional encryption** field shows any applicable additional encryption options.

modules/ocm-settings-tab.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@
99
The **Settings** tab provides a few options for the cluster owner:
1010

1111
ifdef::openshift-rosa[]
12-
* **Monitoring**, which is enabled by default, allows for reporting done on user-defined actions. See link:https://docs.openshift.com/rosa/observability/monitoring/monitoring-overview.html#understanding-the-monitoring-stack_monitoring-overview.html[Understanding the monitoring stack].
12+
* **Monitoring**, which is enabled by default, allows for reporting done on user-defined actions.
1313
endif::openshift-rosa[]
1414
* **Update strategy** allows you to determine if the cluster automatically updates on a certain day of the week at a specified time or if all updates are scheduled manually.
1515
ifdef::openshift-rosa[]

ocm/ocm-overview.adoc

Lines changed: 21 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,14 @@ toc::[]
77

88
{cluster-manager-first} is a managed service where you can install, modify, operate, and upgrade your Red Hat OpenShift clusters. This service allows you to work with all of your organization’s clusters from a single dashboard.
99

10-
{cluster-manager} guides you to install {OCP}, Red Hat OpenShift Service on AWS (ROSA), and {product-short-name} clusters. It is also responsible for managing both {OCP} clusters after self-installation as well as your ROSA and {product-short-name} clusters.
10+
{cluster-manager} guides you to install {OCP}, {product-title}, and {product-short-name} clusters. It is also responsible for managing both {OCP} clusters after self-installation as well as your
11+
ifdef::openshift-rosa[]
12+
{rosa-classic-short}
13+
endif::openshift-rosa[]
14+
ifdef::openshift-rosa-hcp[]
15+
{rosa-short}
16+
endif::openshift-rosa-hcp[]
17+
and {product-short-name} clusters.
1118

1219
You can use {cluster-manager} to do the following actions:
1320

@@ -34,7 +41,10 @@ include::modules/ocm-accessing.adoc[leveloffset=+1]
3441
On the top right of the cluster page, there are some actions that a user can perform on the entire cluster:
3542

3643
* **Open console** launches a web console so that the cluster owner can issue commands to the cluster.
37-
* **Actions** drop-down menu allows the cluster owner to rename the display name of the cluster, change the amount of load balancers and persistent storage on the cluster, if applicable, manually set the node count, and delete the cluster.
44+
* **Actions** drop-down menu allows the cluster owner to rename the display name of the cluster, edit the machine pools, and delete the cluster.
45+
ifdef::openshift-rosa[]
46+
You may also transfer the cluster's ownership to another user.
47+
endif::openshift-rosa[]
3848
* **Refresh** icon forces a refresh of the cluster.
3949

4050
[id="ocm-cluster-tabs"]
@@ -52,14 +62,6 @@ Selecting an active, installed cluster shows tabs associated with that cluster.
5262
* Settings
5363

5464
include::modules/ocm-overview-tab.adoc[leveloffset=+2]
55-
56-
ifndef::openshift-rosa-hcp[]
57-
[role="_additional-resources"]
58-
.Additional resources
59-
60-
* xref:../support/remote_health_monitoring/using-insights-to-identify-issues-with-your-cluster.adoc#using-insights-to-identify-issues-with-your-cluster[Using Insights to identify issues with your cluster]
61-
endif::openshift-rosa-hcp[]
62-
6365
include::modules/ocm-accesscontrol-tab.adoc[leveloffset=+2]
6466
include::modules/ocm-addons-tab.adoc[leveloffset=+2]
6567
include::modules/ocm-cluster-history-tab.adoc[leveloffset=+2]
@@ -74,11 +76,15 @@ include::modules/ocm-settings-tab.adoc[leveloffset=+2]
7476
[id="ocm-additional-resources"]
7577
== Additional resources
7678

77-
* For the complete documentation for {cluster-manager}, see link:https://access.redhat.com/documentation/en-us/openshift_cluster_manager/2022/html-single/managing_clusters/index[{cluster-manager} documentation].
79+
* link:https://access.redhat.com/documentation/en-us/openshift_cluster_manager/2022/html-single/managing_clusters/index[{cluster-manager} documentation]
7880
ifdef::openshift-rosa,openshift-rosa-hcp[]
79-
* For steps to add cluster notification contacts, see xref:../rosa_cluster_admin/rosa-cluster-notifications.adoc#add-notification-contact_rosa-cluster-notifications[Adding cluster notification contacts]
81+
* xref:../rosa_cluster_admin/rosa-cluster-notifications.adoc#add-notification-contact_rosa-cluster-notifications[Adding cluster notification contacts]
82+
* xref:../authentication/sd-configuring-identity-providers.adoc#sd-configuring-identity-providers[Configuring identity providers]
8083
endif::[]
84+
ifndef::openshift-rosa-hcp[]
85+
* xref:../observability/monitoring/about-ocp-monitoring/monitoring-stack-architecture.adoc#understanding-the-monitoring-stack_monitoring-stack-architecture[Understanding the monitoring stack]
86+
* xref:../support/remote_health_monitoring/using-insights-to-identify-issues-with-your-cluster.adoc#using-insights-to-identify-issues-with-your-cluster[Using Insights to identify issues with your cluster]
87+
endif::openshift-rosa-hcp[]
8188
ifdef::openshift-dedicated[]
82-
* For steps to add cluster notification contacts, see xref:../osd_cluster_admin/osd-cluster-notifications.adoc#add-notification-contact_osd-cluster-notifications[Adding cluster notification contacts]
83-
endif::[]
84-
89+
* xref:../osd_cluster_admin/osd-cluster-notifications.adoc#add-notification-contact_osd-cluster-notifications[Adding cluster notification contacts]
90+
endif::[]

0 commit comments

Comments
 (0)