Skip to content

Commit ec5eda9

Browse files
committed
changing instances of Clusters to Cluster List with new OCM UI change
1 parent 3afc9d1 commit ec5eda9

22 files changed

+27
-27
lines changed

modules/access-service.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ cluster, you can access the service by using the OpenShift web console.
1919

2020
.Procedure
2121

22-
. Navigate to the *Clusters* page in {cluster-manager-url}.
22+
. Navigate to the *Cluster List* page in {cluster-manager-url}.
2323

2424
. Select the cluster with an installed service you want to access.
2525

modules/add-user.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Administrator roles are managed using a `dedicated-admins` group on the cluster.
1111

1212
.Procedure
1313

14-
. Navigate to the *Clusters* page and select the cluster you want to add users to.
14+
. Navigate to the *Cluster List* page and select the cluster you want to add users to.
1515

1616
. Click the *Access control* tab.
1717

modules/adding-service-existing.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ To add a service to a cluster, you must be the cluster owner.
3030

3131
.Procedure
3232

33-
. Navigate to the *Clusters* page in {cluster-manager-url}.
33+
. Navigate to the *Cluster List* page in {cluster-manager-url}.
3434

3535
. Select the cluster you want to add a service to.
3636

modules/config-github-idp.adoc

+2-2
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Configuring GitHub authentication allows users to log in to {product-title} with
2323
2424
.Procedure
2525

26-
. From {cluster-manager-url}, navigate to the *Clusters* page and select the cluster that you need to configure identity providers for.
26+
. From {cluster-manager-url}, navigate to the *Cluster List* page and select the cluster that you need to configure identity providers for.
2727

2828
. Click the *Access control* tab.
2929

@@ -67,4 +67,4 @@ https://oauth-openshift.apps.openshift-cluster.example.com/oauth2callback/github
6767

6868
.Verification
6969

70-
* The configured identity provider is now visible on the *Access control* tab of the *Clusters* page.
70+
* The configured identity provider is now visible on the *Access control* tab of the *Cluster List* page.

modules/config-gitlab-idp.adoc

+2-2
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Configure a GitLab identity provider to use link:https://gitlab.com/[GitLab.com]
1717
1818
.Procedure
1919

20-
. From {cluster-manager-url}, navigate to the *Clusters* page and select the cluster that you need to configure identity providers for.
20+
. From {cluster-manager-url}, navigate to the *Cluster List* page and select the cluster that you need to configure identity providers for.
2121

2222
. Click the *Access control* tab.
2323

@@ -57,4 +57,4 @@ https://oauth-openshift.apps.openshift-cluster.example.com/oauth2callback/gitlab
5757

5858
.Verification
5959

60-
* The configured identity provider is now visible on the *Access control* tab of the *Clusters* page.
60+
* The configured identity provider is now visible on the *Access control* tab of the *Cluster List* page.

modules/config-google-idp.adoc

+2-2
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ You can limit authentication to members of a specific hosted domain with the
2020

2121
.Procedure
2222

23-
. From {cluster-manager-url}, navigate to the *Clusters* page and select the cluster that you need to configure identity providers for.
23+
. From {cluster-manager-url}, navigate to the *Cluster List* page and select the cluster that you need to configure identity providers for.
2424

2525
. Click the *Access control* tab.
2626

@@ -58,4 +58,4 @@ https://oauth-openshift.apps.openshift-cluster.example.com/oauth2callback/google
5858

5959
.Verification
6060

61-
* The configured identity provider is now visible on the *Access control* tab of the *Clusters* page.
61+
* The configured identity provider is now visible on the *Access control* tab of the *Cluster List* page.

modules/config-htpasswd-idp.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ The htpasswd identity provider option is included only to enable the creation of
2727

2828
.Procedure
2929

30-
. From {cluster-manager-url}, navigate to the *Clusters* page and select your cluster.
30+
. From {cluster-manager-url}, navigate to the *Cluster List* page and select your cluster.
3131

3232
. Select *Access control* -> *Identity providers*.
3333

modules/config-ldap-idp.adoc

+2-2
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ If the LDAP directory requires authentication to search, specify a `bindDN` and
5555
5656
.Procedure
5757

58-
. From {cluster-manager-url}, navigate to the *Clusters* page and select the cluster that you need to configure identity providers for.
58+
. From {cluster-manager-url}, navigate to the *Cluster List* page and select the cluster that you need to configure identity providers for.
5959

6060
. Click the *Access control* tab.
6161

@@ -94,4 +94,4 @@ If you are using an insecure LDAP connection (ldap:// or port 389), then you mus
9494

9595
.Verification
9696

97-
* The configured identity provider is now visible on the *Access control* tab of the *Clusters* page.
97+
* The configured identity provider is now visible on the *Access control* tab of the *Cluster List* page.

modules/config-openid-idp.adoc

+2-2
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ for more information.
5757
5858
.Procedure
5959

60-
. From {cluster-manager-url}, navigate to the *Clusters* page and select the cluster that you need to configure identity providers for.
60+
. From {cluster-manager-url}, navigate to the *Cluster List* page and select the cluster that you need to configure identity providers for.
6161

6262
. Click the *Access control* tab.
6363

@@ -105,4 +105,4 @@ https://oauth-openshift.apps.openshift-cluster.example.com/oauth2callback/openid
105105

106106
.Verification
107107

108-
* The configured identity provider is now visible on the *Access control* tab of the *Clusters* page.
108+
* The configured identity provider is now visible on the *Access control* tab of the *Cluster List* page.

modules/deleting-machine-pools-ocm.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ ifndef::openshift-rosa[]
2828
endif::openshift-rosa[]
2929

3030
.Procedure
31-
. From {cluster-manager-url}, navigate to the *Clusters* page and select the cluster that contains the machine pool that you want to delete.
31+
. From {cluster-manager-url}, navigate to the *Cluster List* page and select the cluster that contains the machine pool that you want to delete.
3232

3333
. On the selected cluster, select the *Machine pools* tab.
3434

modules/deleting-machine-pools.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ ifndef::openshift-rosa[]
2525
* You have an existing machine pool without any taints and with at least two replicas for a Single-AZ cluster or three replicas for a Multi-AZ cluster.
2626
2727
.Procedure
28-
. From {cluster-manager-url}, navigate to the *Clusters* page and select the cluster that contains the machine pool that you want to delete.
28+
. From {cluster-manager-url}, navigate to the *Cluster List* page and select the cluster that contains the machine pool that you want to delete.
2929

3030
. On the selected cluster, select the *Machine pools* tab.
3131

modules/deleting-service.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ cluster by using {cluster-manager-first}.
1414

1515
.Procedure
1616

17-
. Navigate to the *Clusters* page in {cluster-manager-url}.
17+
. Navigate to the *Cluster List* page in {cluster-manager-url}.
1818

1919
. Click the cluster with the installed service that you want to delete.
2020

modules/deploy-app.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ endif::[]
2828
2929
.Procedure
3030

31-
. Go to the *Clusters* page in {cluster-manager-url}.
31+
. Go to the *Cluster List* page in {cluster-manager-url}.
3232

3333
. Click the options icon (⋮) next to the cluster you want to view.
3434

modules/insights-operator-manual-upload.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ If the operation is successful, the command returns a `"request_id"` and `"accou
6060

6161
. Log in to link:https://console.redhat.com/openshift[].
6262

63-
. Click the *Clusters* menu in the left pane.
63+
. Click the *Cluster List* menu in the left pane.
6464

6565
. To display the details of the cluster, click the cluster name.
6666

modules/insights-operator-register-disconnected-cluster.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ By registering your disconnected cluster, you can continue to report your subscr
2222
.Procedure
2323
. Go to the link:https://console.redhat.com/openshift/register[*Register disconnected cluster*] web page on the {hybrid-console}.
2424

25-
. Optional: To access the *Register disconnected cluster* web page from the home page of the {hybrid-console}, go to the *Clusters* navigation menu item and then select the *Register cluster* button.
25+
. Optional: To access the *Register disconnected cluster* web page from the home page of the {hybrid-console}, go to the *Cluster List* navigation menu item and then select the *Register cluster* button.
2626

2727
. Enter your cluster's details in the provided fields on the *Register disconnected cluster* page.
2828

modules/ocm-disabling-autoscaling-nodes.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Disable autoscaling for worker nodes in the machine pool definition from {cluste
1212

1313
.Procedure
1414

15-
. From {cluster-manager-url}, navigate to the *Clusters* page and select the cluster with autoscaling that must be disabled.
15+
. From {cluster-manager-url}, navigate to the *Cluster List* page and select the cluster with autoscaling that must be disabled.
1616

1717
. On the selected cluster, select the *Machine pools* tab.
1818

modules/ocm-enabling-autoscaling-nodes.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Enable autoscaling for worker nodes in the machine pool definition from {cluster
1212

1313
.Procedure
1414

15-
. From {cluster-manager-url}, navigate to the *Clusters* page and select the cluster that you want to enable autoscaling for.
15+
. From {cluster-manager-url}, navigate to the *Cluster List* page and select the cluster that you want to enable autoscaling for.
1616

1717
. On the selected cluster, select the *Machine pools* tab.
1818

modules/reviewing-cluster-status-from-the-openshift-cluster-manager.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ From the {product-title} web console, you can review detailed information about
1313
* You have access to the cluster as a user with the `cluster-admin` role.
1414
1515
.Procedure
16-
. Go to the *Clusters* list in {cluster-manager-url} and locate your {product-title} cluster.
16+
. Go to the *Cluster List* list in {cluster-manager-url} and locate your {product-title} cluster.
1717
. Click the *Overview* tab for your cluster.
1818
. Review the following information about your cluster:
1919
+

modules/rosa-delete-users.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,6 @@ You can revoke the `dedicated-admin` or `cluster-admin` access of users through
1616
1717
.Procedure
1818

19-
. On the *Clusters* tab of {cluster-manager}, select the name of your cluster to view the cluster details.
19+
. On the *Cluster List* tab of {cluster-manager}, select the name of your cluster to view the cluster details.
2020
. Select *Access control* > *Cluster Roles and Access*.
2121
. For the user that you want to remove, click the *Options* menu {kebab} to the right of the user and group combination and click *Delete*.

modules/support-get-cluster-id.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ endif::openshift-rosa,openshift-dedicated[]
2121
.Procedure
2222
ifdef::openshift-rosa,openshift-dedicated[]
2323
* To manually obtain your cluster ID using {cluster-manager-url}:
24-
.. Navigate to *Clusters*.
24+
.. Navigate to *Cluster List*.
2525
.. Click on the name of the cluster you need to open a support case for.
2626
.. Find the value in the *Cluster ID* field of the *Details* section of the *Overview* tab.
2727
endif::[]

modules/support-reviewing-an-access-request-from-the-hybrid-console.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ endif::openshift-rosa,openshift-dedicated[]
1717

1818
.Procedure
1919

20-
. Navigate to {cluster-manager-url} and select *Clusters*.
20+
. Navigate to {cluster-manager-url} and select *Cluster List*.
2121

2222
. Click the cluster name to review the *Access Request*.
2323

modules/support-submitting-a-case.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ endif::openshift-rosa,openshift-dedicated[]
5858
ifdef::openshift-dedicated[]
5959
+
6060
* To manually obtain your cluster ID using {cluster-manager-url}:
61-
.. Navigate to *Clusters*.
61+
.. Navigate to *Cluster List*.
6262
.. Click on the name of the cluster you need to open a support case for.
6363
.. Find the value in the *Cluster ID* field of the *Details* section of the *Overview* tab.
6464
endif::openshift-dedicated[]

0 commit comments

Comments
 (0)