Merge pull request #77131 from bhardesty/osdocs-9654-update-managed-resources

OSDOCS-9654: Add core namespaces to list of managed resources

Author: ShaunaDiaz

_topic_maps/_topic_map_osd.yml

@@ -207,7 +207,7 @@ Topics:
   - Name: Diagnosing OpenShift CLI (oc) issues
     File: diagnosing-oc-issues
   - Name: OpenShift Dedicated managed resources
-    File: osd-managed-resources
+    File: sd-managed-resources
     Distros: openshift-dedicated
 ---
 Name: Web console

_topic_maps/_topic_map_rosa.yml

@@ -400,7 +400,7 @@ Topics:
     File: rosa-troubleshooting-deployments
     Distros: openshift-rosa
   - Name: Red Hat OpenShift Service on AWS managed resources
-    File: rosa-managed-resources
+    File: sd-managed-resources
     Distros: openshift-rosa
 ---
 Name: Web console

_topic_maps/_topic_map_rosa_hcp.yml

@@ -382,7 +382,7 @@ Topics:
 #     File: rosa-troubleshooting-deployments
 #     Distros: openshift-rosa-hcp
 #   - Name: Red Hat OpenShift Service on AWS managed resources
-#     File: rosa-managed-resources
+#     File: sd-managed-resources
 #     Distros: openshift-rosa-hcp
 # ---
 # Name: Web console

support/troubleshooting/osd-managed-resources.adoc

@@ -1,17 +1,17 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="rosa-managed-resources"]
+[id="sd-managed-resources"]
 = {product-title} managed resources
 include::_attributes/attributes-openshift-dedicated.adoc[]
-:context: rosa-managed-resources
+:context: sd-managed-resources
 
 toc::[]
 
-[id="rosa-managed-resources-overview"]
+[id="sd-managed-resources-overview_{context}"]
 == 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"]
+[id="sd-managed-resources-all_{context}"]
 == 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 ocm-feedback@redhat.com if {cluster-manager} does not support modifying the resources in question.
@@ -25,7 +25,21 @@ include::https://raw.githubusercontent.com/openshift/managed-cluster-config/mast
 ----
 ====
 
-[id="rosa-add-on-managed-namespaces"]
+[id="sd-core-namespaces_{context}"]
+== {product-title} core namespaces
+
+{product-title} core namespaces are installed by default during cluster installation.
+
+.List of core namespaces
+[%collapsible]
+====
+[source,yaml]
+----
+include::https://raw.githubusercontent.com/openshift/managed-cluster-config/master/deploy/osd-managed-resources/ocp-namespaces.ConfigMap.yaml[]
+----
+====
+
+[id="sd-add-on-managed-namespaces_{context}"]
 == {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{nbsp}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.
@@ -39,7 +53,7 @@ include::https://raw.githubusercontent.com/openshift/managed-cluster-config/mast
 ----
 ====
 
-[id="rosa-validating-webhooks"]
+[id="sd-validating-webhooks_{context}"]
 == {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.