Merge pull request #81587 from adellape/reverts_hcp_classic

[main] Reverts for OSDOCS-11534 stories

Author: adellape

_topic_maps/_topic_map_rosa_hcp.yml

@@ -547,47 +547,47 @@ Topics:
 - Name: Cluster notifications
   File: rosa-cluster-notifications
   Distros: openshift-rosa-hcp
-- Name: Configuring private connections
-  Dir: cloud_infrastructure_access
-  Distros: openshift-rosa-hcp
-  Topics:
-  - Name: Configuring private connections
-    File: rosa-configuring-private-connections
-  - Name: Configuring AWS VPC peering
-    File: dedicated-aws-peering
-  - Name: Configuring AWS VPN
-    File: dedicated-aws-vpn
-  - Name: Configuring AWS Direct Connect
-    File: dedicated-aws-dc
-# - Name: Cluster autoscaling  # Cluster autoscaling not supported on HCP
+# - Name: Configuring private connections
+#   Dir: cloud_infrastructure_access
+#   Distros: openshift-rosa-hcp
+#   Topics:
+#   - Name: Configuring private connections
+#     File: rosa-configuring-private-connections
+#   - Name: Configuring AWS VPC peering
+#     File: dedicated-aws-peering
+#   - Name: Configuring AWS VPN
+#     File: dedicated-aws-vpn
+#   - Name: Configuring AWS Direct Connect
+#     File: dedicated-aws-dc
+# - Name: Cluster autoscaling
 #   File: rosa-cluster-autoscaling
-- Name: Manage nodes using machine pools
-  Dir: rosa_nodes
-  Distros: openshift-rosa-hcp
-  Topics:
-  - Name: About machine pools
-    File: rosa-nodes-machinepools-about
-  - Name: Managing compute nodes
-    File: rosa-managing-worker-nodes
-# Local zones not yet implemented in HCP
-    # - Name: Configuring machine pools in Local Zones
-    #   File: rosa-nodes-machinepools-configuring
-  - Name: About autoscaling nodes on a cluster
-    File: rosa-nodes-about-autoscaling-nodes
-  - Name: Configuring cluster memory to meet container memory and risk requirements
-    File: nodes-cluster-resource-configure
+# - Name: Manage nodes using machine pools
+#   Dir: rosa_nodes
+#   Distros: openshift-rosa-hcp
+#   Topics:
+#   - Name: About machine pools
+#     File: rosa-nodes-machinepools-about
+#   - Name: Managing compute nodes
+#     File: rosa-managing-worker-nodes
+#   - Name: Configuring machine pools in Local Zones
+#     File: rosa-nodes-machinepools-configuring
+#     Distros: openshift-rosa-hcp
+#   - Name: About autoscaling nodes on a cluster
+#     File: rosa-nodes-about-autoscaling-nodes
+#   - Name: Configuring cluster memory to meet container memory and risk requirements
+#     File: nodes-cluster-resource-configure
 - Name: Configuring PID limits
   File: rosa-configuring-pid-limits
-  Distros: openshift-rosa-hcp
----
-Name: Security and compliance
-Dir: security
-Distros: openshift-rosa-hcp
-Topics:
+  Distros: openshift-rosa
+# ---
+# Name: Security and compliance
+# Dir: security
+# Distros: openshift-rosa-hcp
+# Topics:
 # - Name: Audit logs
 #   File: audit-log-view
-- Name: Adding additional constraints for IP-based AWS role assumption
-  File: rosa-adding-additional-constraints-for-ip-based-aws-role-assumption
+# - Name: Adding additional constraints for IP-based AWS role assumption
+#   File: rosa-adding-additional-constraints-for-ip-based-aws-role-assumption
 # - Name: Security
 #   File: rosa-security
 # - Name: Application and cluster compliance
@@ -676,6 +676,13 @@ Name: Upgrading
 Dir: upgrading
 Distros: openshift-rosa-hcp
 Topics:
+# - Name: Preparing to upgrade ROSA to 4.9
+#   File: rosa-upgrading-cluster-prepare
+#   Distros: openshift-rosa-hcp
+# - Name: Upgrading ROSA with STS
+#   File: rosa-upgrading-sts
+# - Name: Upgrading ROSA
+#   File: rosa-upgrading
 - Name: Upgrading ROSA with HCP
   File: rosa-hcp-upgrading
 # ---

modules/configuring-machine-pool-disk-volume-cli.adoc

@@ -18,7 +18,7 @@
 ----
 $ rosa create cluster --worker-disk-size=<disk_size>
 ----
-The value can be in GB, GiB, TB, or TiB. Replace `<disk_size>` with a numeric value and unit, for example `--worker-disk-size=200GiB`. You cannot separate the digit and the unit. No spaces are allowed.
+The value can be in GB, GiB, TB, or TiB. Replace '<disk_size>' with a numeric value and unit, for example '--worker-disk-size=200GiB'. You cannot separate the digit and the unit. No spaces are allowed.
 
 .Prerequisite for machine pool creation
 
@@ -30,9 +30,9 @@ The value can be in GB, GiB, TB, or TiB. Replace `<disk_size>` with a numeric va
 +
 [source,terminal]
 ----
-$ rosa create machinepool --cluster=<cluster_id> \// <1>
-                          --disk-size=<disk_size> // <2>
+$ rosa create machinepool --cluster=<cluster_id>  <1>
+                          --disk-size=<disk_size>  <2>
 ----
-<1> Specifies the ID or name of your existing OpenShift cluster.
-<2> Specifies the worker node disk size. The value can be in GB, GiB, TB, or TiB. Replace `<disk_size>` with a numeric value and unit, for example `--disk-size=200GiB`. You cannot separate the digit and the unit. No spaces are allowed.
+<1> Specifies the ID or name of your existing OpenShift cluster
+<2> Specifies the worker node disk size. The value can be in GB, GiB, TB, or TiB. Replace '<disk_size>' with a numeric value and unit, for example '--disk-size=200GiB'. You cannot separate the digit and the unit. No spaces are allowed.
 . Confirm new machine pool disk volume size by logging into the AWS console and find the EC2 virtual machine root volume size.