OSDOCS-3136: Update Dedicated and ROSA troubleshooting content

Author: bmcelvee

_attributes/attributes-openshift-dedicated.adoc

@@ -24,4 +24,6 @@
 :rhoda-short: RHODA
 :rhods: Red Hat OpenShift Data Science
 :osd: OpenShift Dedicated
-
+//Formerly known as CodeReady Containers and CodeReady Workspaces
+:openshift-local-productname: Red Hat OpenShift Local
+:openshift-dev-spaces-productname: Red Hat OpenShift Dev Spaces

_topic_maps/_topic_map_osd.yml

@@ -401,8 +401,8 @@ Topics:
     File: about-remote-health-monitoring
   - Name: Showing data collected by remote health monitoring
     File: showing-data-collected-by-remote-health-monitoring
-  - Name: Opting out of remote health reporting
-    File: opting-out-of-remote-health-reporting
+#  - Name: Opting out of remote health reporting
+#    File: opting-out-of-remote-health-reporting
   - Name: Using Insights to identify issues with your cluster
     File: using-insights-to-identify-issues-with-your-cluster
 - Name: Summarizing cluster specifications

_topic_maps/_topic_map_rosa.yml

@@ -604,3 +604,5 @@ Topics:
   File: rosa-troubleshooting-iam-resources
 - Name: Troubleshooting cluster deployments
   File: rosa-troubleshooting-deployments
+- Name: Red Hat OpenShift Service on AWS managed resources
+  File: rosa-managed-resources

osd_support/osd-managed-resources.adoc

@@ -28,7 +28,7 @@ include::https://raw.githubusercontent.com/openshift/managed-cluster-config/mast
 [id="osd-add-on-managed-namespaces"]
 == {product-title} add-on namespaces
 
-{product-title} add-ons are services available for installation after cluster installation. These additional services include AWS CloudWatch, Red Hat CodeReady Workspaces, Red Hat OpenShift API Management, and Cluster Logging Operator. Any changes to resources within the following namespaces might be overridden by the add-on during upgrades, which can lead to unsupported configurations for the add-on functionality.
+{product-title} add-ons are services available for installation after cluster installation. These additional services include {openshift-dev-spaces-productname}, Red Hat OpenShift API Management, and Cluster Logging Operator. Any changes to resources within the following namespaces can be overridden by the add-on during upgrades, which can lead to unsupported configurations for the add-on functionality.
 
 .List of add-on managed namespaces
 [%collapsible]
@@ -42,7 +42,7 @@ include::https://raw.githubusercontent.com/openshift/managed-cluster-config/mast
 [id="osd-validating-webhooks"]
 == {product-title} validating webhooks
 
-{product-title} validating webhooks are a set of dynamic admission controls maintained by the OpenShift SRE team. These HTTP callbacks, also known as webhooks, are called for various types of requests to ensure cluster stability. Upon request the webhooks accept or reject the request. The following list describes the various webhooks with rules containing the registered operations and resources that are controlled. Any attempt to circumvent these validating webhooks could affect the stability and supportability of the cluster.
+{product-title} validating webhooks are a set of dynamic admission controls maintained by the OpenShift SRE team. These HTTP callbacks, also known as webhooks, are called for various types of requests to ensure cluster stability. The following list describes the various webhooks with rules containing the registered operations and resources that are controlled. Any attempt to circumvent these validating webhooks could affect the stability and supportability of the cluster.
 
 .List of validating webhooks
 [%collapsible]

osd_support/remote_health_monitoring/about-remote-health-monitoring.adoc

@@ -58,15 +58,15 @@ ifndef::openshift-dedicated[]
 
 * See the link:https://github.com/openshift/cluster-monitoring-operator/blob/master/manifests/0000_50_cluster-monitoring-operator_04-config.yaml[upstream cluster-monitoring-operator source code] for a list of the attributes that Telemetry gathers from Prometheus.
 
-* Telemetry is installed and enabled by default. If you need to opt out of remote health reporting, see xref:../../osd_support/remote_health_monitoring/opting-out-of-remote-health-reporting.adoc#opting-out-remote-health-reporting[Opting out of remote health reporting].
+* Telemetry is installed and enabled by default.
 endif::[]
 
 include::modules/insights-operator-about.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
 
-* The Insights Operator is installed and enabled by default. If you need to opt out of remote health reporting, see xref:../../osd_support/remote_health_monitoring/opting-out-of-remote-health-reporting.adoc#opting-out-remote-health-reporting[Opting out of remote health reporting].
+* The Insights Operator is installed and enabled by default.
 
 ifdef::openshift-dedicated[]
 // TODO: When you click on that link, you actually can't opt out. Should this additional resources link be removed?
@@ -114,9 +114,8 @@ Red Hat may share the data collected through Telemetry and the Insights Operator
 
 Red Hat may engage certain third parties to assist in the collection, analysis, and storage of the Telemetry and configuration data.
 
-.User control / enabling and disabling telemetry and configuration data collection
+//.User control / enabling and disabling telemetry and configuration data collection
 
-You may disable {product-title} Telemetry and the Insights Operator by following the instructions in xref:../../osd_support/remote_health_monitoring/opting-out-of-remote-health-reporting.adoc#opting-out-remote-health-reporting[Opting out of remote health reporting].
 
 ifdef::openshift-dedicated[]
 // TODO: Same question about should this be removed or updated, since you can't actually opt out for dedicated?

rosa_support/rosa-managed-resources.adoc

@@ -0,0 +1,54 @@
+:_content-type: ASSEMBLY
+[id="rosa-managed-resources"]
+= {product-title} managed resources
+include::_attributes/attributes-openshift-dedicated.adoc[]
+:context: rosa-managed-resources
+
+toc::[]
+
+[id="rosa-managed-resources-overview"]
+== Overview
+
+The following covers all resources managed or protected by the Service Reliability Engineering Platform (SRE-P) Team.  Customers should not attempt to modify these resources because doing so can lead to cluster instability.
+
+[id="rosa-managed-resources-all"]
+== Hive managed resources
+
+The following list displays the {product-title} resources managed by OpenShift Hive, the centralized fleet configuration management system. These resources are in addition to the OpenShift Container Platform resources created during installation. OpenShift Hive continually attempts to maintain consistency across all {product-title} clusters. Changes to {product-title} resources should be made through {cluster-manager} so that {cluster-manager} and Hive are synchronized. Contact [email protected] if {cluster-manager} does not support modifying the resources in question.
+
+.List of Hive managed resources
+[%collapsible]
+====
+[source,yaml]
+----
+include::https://raw.githubusercontent.com/openshift/managed-cluster-config/master/resources/managed/all-osd-resources.yaml[]
+----
+====
+
+[id="rosa-add-on-managed-namespaces"]
+== {product-title} add-on namespaces
+
+{product-title} add-ons are services available for installation after cluster installation. These additional services include {openshift-dev-spaces-productname}, Red Hat OpenShift API Management, and Cluster Logging Operator. Any changes to resources within the following namespaces can be overridden by the add-on during upgrades, which can lead to unsupported configurations for the add-on functionality.
+
+.List of add-on managed namespaces
+[%collapsible]
+====
+[source,yaml]
+----
+include::https://raw.githubusercontent.com/openshift/managed-cluster-config/master/resources/addons-namespaces/main.yaml[]
+----
+====
+
+[id="rosa-validating-webhooks"]
+== {product-title} validating webhooks
+
+{product-title} validating webhooks are a set of dynamic admission controls maintained by the OpenShift SRE team. These HTTP callbacks, also known as webhooks, are called for various types of requests to ensure cluster stability. The following list describes the various webhooks with rules containing the registered operations and resources that are controlled. Any attempt to circumvent these validating webhooks could affect the stability and supportability of the cluster.
+
+.List of validating webhooks
+[%collapsible]
+====
+[source,json]
+----
+include::https://raw.githubusercontent.com/openshift/managed-cluster-validating-webhooks/master/docs/webhooks.json[]
+----
+====