OSDOCS-11831: Add Support book to ROSA HCP

Author: bhardesty

_topic_maps/_topic_map_osd.yml

@@ -210,9 +210,8 @@ Topics:
     File: troubleshooting-operator-issues
   - Name: Investigating pod issues
     File: investigating-pod-issues
-# Hiding from ROSA and OSD until it is decided who should port the Build book
-#  - Name: Troubleshooting the Source-to-Image process
-#    File: troubleshooting-s2i
+  - Name: Troubleshooting the Source-to-Image process
+    File: troubleshooting-s2i
   - Name: Troubleshooting storage issues
     File: troubleshooting-storage-issues
 # Not supported per WINC team

_topic_maps/_topic_map_rosa.yml

@@ -402,9 +402,8 @@ Topics:
     File: troubleshooting-operator-issues
   - Name: Investigating pod issues
     File: investigating-pod-issues
-# Hiding from ROSA and OSD until it is decided who should port the Build book
-#  - Name: Troubleshooting the Source-to-Image process
-#    File: troubleshooting-s2i
+  - Name: Troubleshooting the Source-to-Image process
+    File: troubleshooting-s2i
   - Name: Troubleshooting storage issues
     File: troubleshooting-storage-issues
 # Not supported per WINC team

_topic_maps/_topic_map_rosa_hcp.yml

@@ -300,6 +300,92 @@ Topics:
   - Name: Least privilege permissions for ROSA CLI commands
     File: rosa-cli-permission-examples
 ---
+Name: Support
+Dir: support
+Distros: openshift-rosa-hcp
+Topics:
+- Name: Support overview
+  File: index
+- Name: Managing your cluster resources
+  File: managing-cluster-resources
+- Name: Approved Access
+  File: approved-access
+- Name: Getting support
+  File: getting-support
+- Name: Remote health monitoring with connected clusters
+  Dir: remote_health_monitoring
+  Topics:
+  - Name: About remote health monitoring
+    File: about-remote-health-monitoring
+  - Name: Showing data collected by remote health monitoring
+    File: showing-data-collected-by-remote-health-monitoring
+# cannot get resource "secrets" in API group "" in the namespace "openshift-config"
+#  - Name: Opting out of remote health reporting
+#    File: opting-out-of-remote-health-reporting
+# cannot get resource "secrets" in API group "" in the namespace "openshift-config"
+#  - Name: Enabling remote health reporting
+#    File: enabling-remote-health-reporting
+  - Name: Using Insights to identify issues with your cluster
+    File: using-insights-to-identify-issues-with-your-cluster
+  - Name: Using Insights Operator
+    File: using-insights-operator
+# Not supported per Michael McNeill
+# - Name: Using remote health reporting in a restricted network
+#   File: remote-health-reporting-from-restricted-network
+# cannot list resource "secrets" in API group "" in the namespace "openshift-config"
+#  - Name: Importing simple content access entitlements with Insights Operator
+#    File: insights-operator-simple-access
+- Name: Gathering data about your cluster
+  File: gathering-cluster-data
+- Name: Summarizing cluster specifications
+  File: summarizing-cluster-specifications
+- Name: Troubleshooting
+  Dir: troubleshooting
+  Topics:
+# rosa has own troubleshooting installations
+#  - Name: Troubleshooting installations
+#    File: troubleshooting-installations
+  - Name: Troubleshooting ROSA installations
+    File: rosa-troubleshooting-installations
+  - Name: Troubleshooting networking
+    File: rosa-troubleshooting-networking
+  - Name: Verifying node health
+    File: verifying-node-health
+#  cannot create resource "namespaces", cannot patch resource "nodes"
+#  - Name: Troubleshooting CRI-O container runtime issues
+#    File: troubleshooting-crio-issues
+# requires ostree, butane, and other plug-ins
+#  - Name: Troubleshooting operating system issues
+#    File: troubleshooting-operating-system-issues
+#    Distros: openshift-rosa
+# cannot patch resource "nodes", "nodes/proxy", "namespaces"
+#  - Name: Troubleshooting network issues
+#    File: troubleshooting-network-issues
+#    Distros: openshift-rosa
+  - Name: Troubleshooting Operator issues
+    File: troubleshooting-operator-issues
+  - Name: Investigating pod issues
+    File: investigating-pod-issues
+  - Name: Troubleshooting the Source-to-Image process
+    File: troubleshooting-s2i
+  - Name: Troubleshooting storage issues
+    File: troubleshooting-storage-issues
+# Not supported per WINC team
+#  - Name: Troubleshooting Windows container workload issues
+#    File: troubleshooting-windows-container-workload-issues
+  - Name: Investigating monitoring issues
+    File: investigating-monitoring-issues
+  - Name: Diagnosing OpenShift CLI (oc) issues
+    File: diagnosing-oc-issues
+  - Name: Troubleshooting expired offline access tokens
+    File: rosa-troubleshooting-expired-tokens
+  - Name: Troubleshooting IAM roles
+    File: rosa-troubleshooting-iam-resources
+  - Name: Troubleshooting cluster deployments
+    File: rosa-troubleshooting-deployments
+  - Name: Red Hat OpenShift Service on AWS managed resources
+    File: sd-managed-resources
+---
 Name: Cluster administration
 Dir: rosa_cluster_admin
 Distros: openshift-rosa-hcp

modules/accessing-running-pods.adoc

@@ -10,12 +10,12 @@ You can review running pods dynamically by opening a shell inside a pod or by ga
 
 .Prerequisites
 
-ifndef::openshift-rosa,openshift-dedicated[]
+ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 * You have access to the cluster as a user with the `cluster-admin` role.
-endif::openshift-rosa,openshift-dedicated[]
-ifdef::openshift-rosa,openshift-dedicated[]
+endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
+ifdef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 * You have access to the cluster as a user with the `dedicated-admin` role.
-endif::openshift-rosa,openshift-dedicated[]
+endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 * Your API service is still functional.
 * You have installed the OpenShift CLI (`oc`).
 

modules/cluster-resources.adoc

@@ -6,12 +6,12 @@ You can interact with cluster resources by using the OpenShift CLI (`oc`) tool i
 
 .Prerequisites
 
-ifndef::openshift-rosa,openshift-dedicated[]
+ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 * You have access to the cluster as a user with the `cluster-admin` role.
-endif::openshift-rosa,openshift-dedicated[]
-ifdef::openshift-rosa,openshift-dedicated[]
+endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
+ifdef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 * You have access to the cluster as a user with the `dedicated-admin` role.
-endif::openshift-rosa,openshift-dedicated[]
+endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 * You have access to the web console or you have installed the `oc` CLI tool.
 
 .Procedure

modules/copying-files-pods-and-containers.adoc

@@ -10,12 +10,12 @@ You can copy files to and from a pod to test configuration changes or gather dia
 
 .Prerequisites
 
-ifndef::openshift-rosa,openshift-dedicated[]
+ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 * You have access to the cluster as a user with the `cluster-admin` role.
-endif::openshift-rosa,openshift-dedicated[]
-ifdef::openshift-rosa,openshift-dedicated[]
+endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
+ifdef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 * You have access to the cluster as a user with the `dedicated-admin` role.
-endif::openshift-rosa,openshift-dedicated[]
+endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 * Your API service is still functional.
 * You have installed the OpenShift CLI (`oc`).
 

modules/inspecting-pod-and-container-logs.adoc

@@ -10,12 +10,12 @@ You can inspect pod and container logs for warnings and error messages related t
 
 .Prerequisites
 
-ifndef::openshift-rosa,openshift-dedicated[]
+ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 * You have access to the cluster as a user with the `cluster-admin` role.
-endif::openshift-rosa,openshift-dedicated[]
-ifdef::openshift-rosa,openshift-dedicated[]
+endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
+ifdef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 * You have access to the cluster as a user with the `dedicated-admin` role.
-endif::openshift-rosa,openshift-dedicated[]
+endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 * Your API service is still functional.
 * You have installed the OpenShift CLI (`oc`).
 

modules/monitoring-determining-why-prometheus-is-consuming-disk-space.adoc

@@ -28,12 +28,12 @@ Using attributes that are bound to a limited set of possible values reduces the
 
 .Prerequisites
 
-ifndef::openshift-dedicated,openshift-rosa[]
+ifndef::openshift-dedicated,openshift-rosa-hcp,openshift-rosa[]
 * You have access to the cluster as a user with the `cluster-admin` cluster role.
-endif::openshift-dedicated,openshift-rosa[]
-ifdef::openshift-dedicated,openshift-rosa[]
+endif::openshift-dedicated,openshift-rosa-hcp,openshift-rosa[]
+ifdef::openshift-dedicated,openshift-rosa-hcp,openshift-rosa[]
 * You have access to the cluster as a user with the `dedicated-admin` role.
-endif::openshift-dedicated,openshift-rosa[]
+endif::openshift-dedicated,openshift-rosa-hcp,openshift-rosa[]
 * You have installed the OpenShift CLI (`oc`).
 
 .Procedure
@@ -64,12 +64,12 @@ topk(10, sum by(namespace, job) (sum_over_time(scrape_series_added[1h])))
 * *If the metrics relate to a core {product-title} project*, create a Red Hat support case on the link:https://access.redhat.com/[Red Hat Customer Portal].
 
 . Review the TSDB status using the Prometheus HTTP API by following these steps when logged in as a
-ifndef::openshift-dedicated,openshift-rosa[]
+ifndef::openshift-dedicated,openshift-rosa-hcp,openshift-rosa[]
 cluster administrator:
-endif::openshift-dedicated,openshift-rosa[]
-ifdef::openshift-dedicated,openshift-rosa[]
+endif::openshift-dedicated,openshift-rosa-hcp,openshift-rosa[]
+ifdef::openshift-dedicated,openshift-rosa-hcp,openshift-rosa[]
 `dedicated-admin`:
-endif::openshift-dedicated,openshift-rosa[]
+endif::openshift-dedicated,openshift-rosa-hcp,openshift-rosa[]
 +
 .. Get the Prometheus API route URL by running the following command:
 +

modules/monitoring-investigating-why-user-defined-metrics-are-unavailable.adoc

@@ -11,12 +11,12 @@
 
 .Prerequisites
 
-ifndef::openshift-rosa,openshift-dedicated[]
+ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 * You have access to the cluster as a user with the `cluster-admin` role.
-endif::openshift-rosa,openshift-dedicated[]
-ifdef::openshift-rosa,openshift-dedicated[]
+endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
+ifdef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 * You have access to the cluster as a user with the `dedicated-admin` role.
-endif::openshift-rosa,openshift-dedicated[]
+endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 * You have installed the OpenShift CLI (`oc`).
 * You have enabled and configured monitoring for user-defined projects.
 * You have created a `ServiceMonitor` resource.

modules/monitoring-resolving-the-kubepersistentvolumefillingup-alert-firing-for-prometheus.adoc

@@ -23,12 +23,12 @@ To address this issue, you can remove Prometheus time-series database (TSDB) blo
 
 .Prerequisites
 
-ifndef::openshift-dedicated,openshift-rosa[]
+ifndef::openshift-dedicated,openshift-rosa-hcp,openshift-rosa[]
 * You have access to the cluster as a user with the `cluster-admin` cluster role.
-endif::openshift-dedicated,openshift-rosa[]
-ifdef::openshift-dedicated,openshift-rosa[]
+endif::openshift-dedicated,openshift-rosa-hcp,openshift-rosa[]
+ifdef::openshift-dedicated,openshift-rosa-hcp,openshift-rosa[]
 * You have access to the cluster as a user with the `dedicated-admin` role.
-endif::openshift-dedicated,openshift-rosa[]
+endif::openshift-dedicated,openshift-rosa-hcp,openshift-rosa[]
 * You have installed the OpenShift CLI (`oc`).
 
 .Procedure