Skip to content

Commit

Permalink
OSDOCS-10781
Browse files Browse the repository at this point in the history
  • Loading branch information
jneczypor committed Jun 7, 2024
1 parent 25a77b4 commit 368887b
Show file tree
Hide file tree
Showing 162 changed files with 459 additions and 470 deletions.
8 changes: 4 additions & 4 deletions adding_service_cluster/rosa-available-services.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -22,21 +22,21 @@ include::modules/osd-rhoam.adoc[leveloffset=+1]

[role="_additional-resources"]
.Additional resources
* link:https://access.redhat.com/documentation/en-us/red_hat_openshift_api_management[Red Hat OpenShift API Management] documentation
* link:https://access.redhat.com/documentation/en-us/red_hat_openshift_api_management[Red{nbsp}Hat OpenShift API Management] documentation
////
include::modules/rosa-rhoda.adoc[leveloffset=+1]

[role="_additional-resources"]
.Additional resources

* link:https://www.redhat.com/en/technologies/cloud-computing/openshift/openshift-database-access[Red Hat OpenShift Database Access] product page
* link:https://www.redhat.com/en/technologies/cloud-computing/openshift/openshift-database-access[Red{nbsp}Hat OpenShift Database Access] product page
////
// This module and additional resource are no longer included in the document due to OSDOCS-5817.
include::modules/rosa-rhods.adoc[leveloffset=+1]

[role="_additional-resources"]
.Additional resources
* link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_science/1[Red Hat OpenShift Data Science] documentation
* link:https://www.redhat.com/en/technologies/cloud-computing/openshift/openshift-data-science[Red Hat OpenShift Data Science] product page
* link:https://access.redhat.com/documentation/en-us/red_hat_openshift_data_science/1[Red{nbsp}Hat OpenShift Data Science] documentation
* link:https://www.redhat.com/en/technologies/cloud-computing/openshift/openshift-data-science[Red{nbsp}Hat OpenShift Data Science] product page
2 changes: 1 addition & 1 deletion cli_reference/rosa_cli/rosa-cli-permission-examples.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ You can create roles with permissions that adhere to the principal of least priv

[IMPORTANT]
====
Although the policies and commands presented in this topic will work in conjunction with one another, you might have other restrictions within your AWS environment that make the policies for these commands insufficient for your specific needs. Red Hat provides these examples as a baseline, assuming no other AWS Identity and Access Management (IAM) restrictions are present.
Although the policies and commands presented in this topic will work in conjunction with one another, you might have other restrictions within your AWS environment that make the policies for these commands insufficient for your specific needs. Red{nbsp}Hat provides these examples as a baseline, assuming no other AWS Identity and Access Management (IAM) restrictions are present.
====

[NOTE]
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -194,7 +194,7 @@ stringData:
EOF
----
+
. Install the Red Hat AWS Load Balancer Operator:
. Install the AWS Load Balancer Operator:
+
[source,terminal]
----
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ $ oc get authentication.config.openshift.io cluster -o json \
"https://xxxxx.cloudfront.net/xxxxx"
----
+
If your output is different, do not proceed. See xref:../rosa_install_access_delete_clusters/rosa-sts-creating-a-cluster-quickly.adoc#rosa-sts-creating-a-cluster-quickly[Red Hat documentation on creating an STS cluster] before continuing this process.
If your output is different, do not proceed. See xref:../rosa_install_access_delete_clusters/rosa-sts-creating-a-cluster-quickly.adoc#rosa-sts-creating-a-cluster-quickly[Red{nbsp}Hat documentation on creating an STS cluster] before continuing this process.

. Set the `SecurityContextConstraints` permission to allow the CSI driver to run by running the following command:
+
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ toc::[]

. A Provisioned ROSA cluster
+
This lab assumes you have access to a successfully provisioned a ROSA cluster. If you have not yet created a ROSA cluster, see xref:../../rosa_getting_started/rosa-quickstart-guide-ui.html#rosa-getting-started-prerequisites_rosa-quickstart-guide-ui[Red Hat OpenShift Service on AWS quickstart guide] for more information.
This lab assumes you have access to a successfully provisioned a ROSA cluster. If you have not yet created a ROSA cluster, see xref:../../rosa_getting_started/rosa-quickstart-guide-ui.adoc#rosa-getting-started-prerequisites_rosa-quickstart-guide-ui[Red{nbsp}Hat OpenShift Service on AWS quick start guide] for more information.

. The OpenShift Command Line Interface (CLI)
+
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ toc::[]

While wildcard certificates provide simplicity by securing all first-level subdomains of a given domain with a single certificate, other use cases can require the use of individual certificates per domain.

Learn how to use the link:https://docs.openshift.com/container-platform/latest/security/cert_manager_operator/index.html[cert-manager Operator for Red Hat OpenShift] and link:https://letsencrypt.org/[Let's Encrypt] to dynamically issue certificates for routes created using a custom domain.
Learn how to use the link:https://docs.openshift.com/container-platform/latest/security/cert_manager_operator/index.html[cert-manager Operator for Red{nbsp}Hat OpenShift] and link:https://letsencrypt.org/[Let's Encrypt] to dynamically issue certificates for routes created using a custom domain.

[id="cloud-experts-dynamic-certificate-custom-domain-prerequisites"]
== Prerequisites
Expand Down Expand Up @@ -170,10 +170,10 @@ $ oc new-project cert-manager-operator
+
[IMPORTANT]
====
Do not attempt to use more than one `cert-manager` Operator in your cluster. If you have a community `cert-manager` Operator installed in your cluster, you must uninstall it before installing the `cert-manager` Operator for Red Hat OpenShift.
Do not attempt to use more than one `cert-manager` Operator in your cluster. If you have a community `cert-manager` Operator installed in your cluster, you must uninstall it before installing the `cert-manager` Operator for Red{nbsp}Hat OpenShift.
====
+
. Install the `cert-manager` Operator for Red Hat OpenShift:
. Install the `cert-manager` Operator for Red{nbsp}Hat OpenShift:
+
[source,terminal]
----
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -9,9 +9,9 @@ toc::[]
//rosaworkshop.io content metadata
//Brought into ROSA product docs 2023-11-30

Administration (admin) privileges are not automatically granted to users that you add to your cluster. If you want to grant admin-level privileges to certain users, you will need to manually grant them to each user. You can grant admin privileges from either the ROSA command line interface (CLI) or the Red Hat OpenShift Cluster Manager web user interface (UI).
Administration (admin) privileges are not automatically granted to users that you add to your cluster. If you want to grant admin-level privileges to certain users, you will need to manually grant them to each user. You can grant admin privileges from either the ROSA command line interface (CLI) or the Red{nbsp}Hat OpenShift Cluster Manager web user interface (UI).

Red Hat offers two types of admin privileges:
Red{nbsp}Hat offers two types of admin privileges:

* `cluster-admin`: `cluster-admin` privileges give the admin user full privileges within the cluster.
Expand Down Expand Up @@ -64,7 +64,7 @@ image:cloud-experts-getting-started-admin-rights-admin-panel.png[]
$ oc get all -n openshift-apiserver
----

== Using the Red Hat OpenShift Cluster Manager UI
== Using the Red{nbsp}Hat OpenShift Cluster Manager UI

. Log in to the {cluster-manager-url}.
. Select your cluster.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,7 @@ $ rosa delete account-roles --prefix <prefix> --mode auto --yes

== Deleting a ROSA cluster using the UI

. Log in to the Red Hat OpenShift Cluster Manager, and locate the cluster you want to delete.
. Log in to the {cluster-manager-url}, and locate the cluster you want to delete.

. Click the three dots to the right of the cluster.
+
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -9,14 +9,14 @@ toc::[]
//rosaworkshop.io content metadata
//Brought into ROSA product docs 2023-11-20

This tutorial outlines the detailed steps to deploy a {product-title} (ROSA) cluster using the Red Hat OpenShift Cluster Manager user interface (UI).
This tutorial outlines the detailed steps to deploy a {product-title} (ROSA) cluster using the Red{nbsp}Hat OpenShift Cluster Manager user interface (UI).

== Deployment workflow
The overall deployment workflow follows these steps:

. Create the account wide roles and policies.
. Associate your AWS account with your Red Hat account.
.. Create and link the Red Hat OpenShift Cluster Manager role.
. Associate your AWS account with your Red{nbsp}Hat account.
.. Create and link the Red{nbsp}Hat OpenShift Cluster Manager role.
.. Create and link the user role.
. Create the cluster.

Expand Down Expand Up @@ -56,15 +56,15 @@ I: To create a cluster with these roles, run the following command:
rosa create cluster --sts
----

== Associating your AWS account with your Red Hat account
== Associating your AWS account with your Red{nbsp}Hat account
This step tells the OpenShift Cluster Manager what AWS account you want to use when deploying ROSA.

[NOTE]
====
If you have already associated your AWS accounts, skip this step.
====

. Open the {hybrid-console} by visiting the {cluster-manager-url} and logging in to your Red Hat account.
. Open the {hybrid-console} by visiting the {cluster-manager-url} and logging in to your Red{nbsp}Hat account.

. Click *Create Cluster*.

Expand Down Expand Up @@ -115,7 +115,7 @@ For the purposes of this tutorial, use the *Admin OpenShift Cluster Manager role
$ rosa create ocm-role --mode auto --admin --yes
----
+
This command creates the OpenShift Cluster Manager role and associates it with your Red Hat account.
This command creates the OpenShift Cluster Manager role and associates it with your Red{nbsp}Hat account.
+
.Example output
+
Expand Down Expand Up @@ -159,7 +159,7 @@ As defined in the xref:../../../rosa_architecture/rosa-sts-about-iam-resources.a
$ rosa list user-role
----

. Run the following command to create the user role and to link it to your Red Hat account:
. Run the following command to create the user role and to link it to your Red{nbsp}Hat account:
+
[source,terminal]
----
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ toc::[]

This tutorial outlines deploying a {hcp-title-first} cluster.

With {hcp-title}, you can decouple the control plane from the data plane. This is a new deployment model for ROSA in which the control plane is hosted in a Red Hat-owned AWS account. The control plane is no longer hosted in your AWS account, reducing your AWS infrastructure expenses. The control plane is dedicated to a single cluster and is highly available. For more information, see the xref:../../../rosa_hcp/rosa-hcp-sts-creating-a-cluster-quickly.adoc#rosa-hcp-sts-creating-a-cluster-quickly[{hcp-title} documentation].
With {hcp-title}, you can decouple the control plane from the data plane. This is a new deployment model for ROSA in which the control plane is hosted in a Red{nbsp}Hat-owned AWS account. The control plane is no longer hosted in your AWS account, reducing your AWS infrastructure expenses. The control plane is dedicated to a single cluster and is highly available. For more information, see the xref:../../../rosa_hcp/rosa-hcp-sts-creating-a-cluster-quickly.adoc#rosa-hcp-sts-creating-a-cluster-quickly[{hcp-title} documentation].

== Prerequisites

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ Run the following command _once_ for each AWS account and y-stream OpenShift ver
rosa create account-roles --mode auto --yes
----

== Creating Red Hat OpenShift Cluster Manager roles
== Creating Red{nbsp}Hat OpenShift Cluster Manager roles
. Create one OpenShift Cluster Manager role for each AWS account by running the following command:
+
[source,terminal]
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -18,29 +18,29 @@ You can add additional email addresses for communications about your cluster.
. Click the *Support* tab.
. Click *Add notification contact*, and enter the additional email addresses.

== Contacting Red Hat for support using the UI
== Contacting Red{nbsp}Hat for support using the UI

. On the {cluster-manager} UI, click the *Support* tab.
. Click *Open support case*.

== Contacting Red Hat for support using the support page
== Contacting Red{nbsp}Hat for support using the support page

. Go to the link:https://support.redhat.com[Red Hat support page].
. Go to the link:https://support.redhat.com[Red{nbsp}Hat support page].
. Click *Open a new Case*.
+
image::obtain-support-case.png[]

. Log in to your Red Hat account.
. Log in to your Red{nbsp}Hat account.
. Select the reason for contacting support.
+
image::obtain-support-reason.png[]

. Select *Red Hat OpenShift Service on AWS*.
. Select *Red{nbsp}Hat OpenShift Service on AWS*.

image::obtain-support-select-rosa.png[]

. Click *continue*.
. Enter a summary of the issue and the details of your request. Upload any files, logs, and screenshots. The more details you provide, the better Red Hat support can help your case.
. Enter a summary of the issue and the details of your request. Upload any files, logs, and screenshots. The more details you provide, the better Red{nbsp}Hat support can help your case.
+
[NOTE]
====
Expand All @@ -54,11 +54,11 @@ image::obtain-support-summary.png[]
. Click *Continue*.
. Enter the following information about your case:
.. *Support level:* Premium
.. *Severity:* Review the Red Hat Support Severity Level Definitions to choose the correct one.
.. *Severity:* Review the Red{nbsp}Hat Support Severity Level Definitions to choose the correct one.
.. *Group:* If this is related to a few other cases you can select the corresponding group.
.. *Language*
.. *Send notifications:* Add any additional email addresses to keep notified of activity.
.. *Red Hat associates:* If you are working with anyone from Red Hat and want to keep them in the loop you can enter their email address here.
.. *Red{nbsp}Hat associates:* If you are working with anyone from Red{nbsp}Hat and want to keep them in the loop you can enter their email address here.
.. *Alternate Case ID:* If you want to attach your own ID to it you can enter it here.
. Click *Continue*.
. On the review screen make sure you select the correct cluster ID that you are contacting support about.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ toc::[]
Ways to schedule a cluster upgrade include:

* *Manually using the command line interface (CLI)*: Start a one-time immediate upgrade or schedule a one-time upgrade for a future date and time.
* *Manually using the Red Hat OpenShift Cluster Manager user interface (UI)*: Start a one-time immediate upgrade or schedule a one-time upgrade for a future date and time.
* *Manually using the Red{nbsp}Hat OpenShift Cluster Manager user interface (UI)*: Start a one-time immediate upgrade or schedule a one-time upgrade for a future date and time.
* *Automated upgrades*: Set an upgrade window for recurring y-stream upgrades whenever a new version is available without needing to manually schedule it. Minor versions have to be manually scheduled.
For more details about cluster upgrades, run the following command:
Expand Down
Loading

0 comments on commit 368887b

Please sign in to comment.