OSDOCS-10853 Remove unsupported overcommit methods from Managed docs

Author: laubai

_topic_maps/_topic_map_rosa.yml

@@ -1445,6 +1445,7 @@ Topics:
   - Name: Configuring cluster memory to meet container memory and risk requirements
     File: nodes-cluster-resource-configure
     Distros: openshift-rosa
+# TODO: Remove the whole nodes-cluster-overcommit file for OSDOCS-10853?
   - Name: Configuring your cluster to place pods on overcommited nodes
     File: nodes-cluster-overcommit
     Distros: openshift-rosa

modules/nodes-cluster-overcommit-project-disable.adoc

@@ -7,19 +7,25 @@
 [id="nodes-cluster-overcommit-project-disable_{context}"]
 = Disabling overcommitment for a project
 
+ifndef::openshift-rosa,openshift-rosa-classic,openshift-rosa-hcp,openshift-dedicated[]
 When enabled, overcommitment can be disabled per-project. For example, you can allow infrastructure components to be configured independently of overcommitment.
+endif::openshift-rosa,openshift-rosa-classic,openshift-rosa-hcp,openshift-dedicated[]
+
+ifdef::openshift-rosa,openshift-rosa-classic,openshift-rosa-hcp,openshift-dedicated[]
+If required by your use case, you can disable overcommitment on any project that is not managed by Red Hat. For a list of projects that cannot be modified, see _Red Hat Managed resources_ in _Additional resources_.
+endif::openshift-rosa,openshift-rosa-classic,openshift-rosa-hcp,openshift-dedicated[]
 
 .Procedure
 
 To disable overcommitment in a project:
 
-ifndef::openshift-rosa,openshift-dedicated[]
+ifndef::openshift-rosa,openshift-rosa-classic,openshift-rosa-hcp,openshift-dedicated[]
 . Create or edit the namespace object file.
-endif::openshift-rosa,openshift-dedicated[]
+endif::openshift-rosa,openshift-rosa-classic,openshift-rosa-hcp,openshift-dedicated[]
 // Invalid value: "false": field is immutable, try updating the namespace
-ifdef::openshift-rosa,openshift-dedicated[]
+ifdef::openshift-rosa,openshift-rosa-classic,openshift-rosa-hcp,openshift-dedicated[]
 . Edit the namespace object file.
-endif::openshift-rosa,openshift-dedicated[]
+endif::openshift-rosa,openshift-rosa-classic,openshift-rosa-hcp,openshift-dedicated[]
 
 . Add the following annotation:
 +

nodes/clusters/nodes-cluster-overcommit.adoc

@@ -6,11 +6,6 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-
-
-
-
-
 In an _overcommitted_ state, the sum of the container compute resource requests
 and limits exceeds the resources available on the system. For example, you might
 want to use overcommitment in development environments where a trade-off of
@@ -24,33 +19,32 @@ The scheduler attempts to optimize the compute resource use across all nodes
 in your cluster. It places pods onto specific nodes, taking the pods' compute
 resource requests and nodes' available capacity into consideration.
 
-ifndef::openshift-rosa,openshift-dedicated[]
+ifndef::openshift-rosa,openshift-rosa-classic,openshift-rosa-hcp,openshift-dedicated[]
 {product-title} administrators can control the level of overcommit and manage
 container density on nodes. You can configure cluster-level overcommit using
 the xref:#nodes-cluster-resource-override_nodes-cluster-overcommit[ClusterResourceOverride Operator]
 to override the ratio between requests and limits set on developer containers.
 In conjunction with xref:#nodes-cluster-node-overcommit_nodes-cluster-overcommit[node overcommit] and
 xref:../../applications/deployments/managing-deployment-processes.adoc#deployments-setting-resources_deployment-operations[project memory and CPU limits and defaults], you can adjust the resource limit and request to achieve the desired level of overcommit.
-endif::openshift-rosa,openshift-dedicated[]
-ifdef::openshift-rosa,openshift-dedicated[]
-{product-title} administrators can control the level of overcommit and manage
-container density on nodes. You can configure cluster-level overcommit using
-the xref:#nodes-cluster-resource-override_nodes-cluster-overcommit[ClusterResourceOverride Operator]
-to override the ratio between requests and limits set on developer containers.
-In conjunction with xref:#nodes-cluster-node-overcommit_nodes-cluster-overcommit[node overcommit], you can adjust the resource limit and request to achieve the desired level of overcommit.
-endif::openshift-rosa,openshift-dedicated[]
 
 [NOTE]
 ====
 In {product-title}, you must enable cluster-level overcommit. Node overcommitment is enabled by default.
 See xref:#nodes-cluster-overcommit-node-disable_nodes-cluster-overcommit[Disabling overcommitment for a node].
 ====
+endif::openshift-rosa,openshift-rosa-classic,openshift-rosa-hcp,openshift-dedicated[]
+
+//ROSA and Dedicated intro
+ifdef::openshift-rosa,openshift-rosa-classic,openshift-rosa-hcp,openshift-dedicated[]
+{product-title} administrators can manage container density on nodes by configuring pod placement behavior. Administrators can also optionally disable project-level overcommit behavior on customer-created namespaces only.
+endif::openshift-rosa,openshift-rosa-classic,openshift-rosa-hcp,openshift-dedicated[]
 
 // The following include statements pull in the module files that comprise
 // the assembly. Include any combination of concept, procedure, or reference
 // modules required to cover the user story. You can also include other
 // assemblies.
 
+ifndef::openshift-rosa,openshift-rosa-classic,openshift-rosa-hcp,openshift-dedicated[]
 
 include::modules/nodes-cluster-overcommit-resource-requests.adoc[leveloffset=+1]
 
@@ -72,6 +66,7 @@ include::modules/nodes-qos-about-swap.adoc[leveloffset=+2]
 
 include::modules/nodes-cluster-overcommit-configure-nodes.adoc[leveloffset=+2]
 
+//TODO: Omit just this file for OSDOCS-10853? Or omit this entire chapter?
 include::modules/nodes-cluster-overcommit-node-enforcing.adoc[leveloffset=+2]
 
 include::modules/nodes-cluster-overcommit-node-resources.adoc[leveloffset=+2]
@@ -82,11 +77,20 @@ include::modules/nodes-cluster-project-overcommit.adoc[leveloffset=+1]
 
 include::modules/nodes-cluster-overcommit-project-disable.adoc[leveloffset=+2]
 
-ifndef::openshift-rosa,openshift-dedicated[]
+endif::openshift-rosa,openshift-rosa-classic,openshift-rosa-hcp,openshift-dedicated[]
+
+//ROSA and Dedicated can only do this
+ifdef::openshift-rosa,openshift-rosa-classic,openshift-rosa-hcp,openshift-dedicated[]
+include::modules/nodes-cluster-overcommit-project-disable.adoc[leveloffset=+1]
+endif::openshift-rosa,openshift-rosa-classic,openshift-rosa-hcp,openshift-dedicated[]
+
 [role="_additional-resources"]
 [id="nodes-cluster-overcommit-addtl-resources"]
 == Additional resources
-
+ifndef::openshift-rosa,openshift-rosa-classic,openshift-rosa-hcp,openshift-dedicated[]
 * xref:../../applications/deployments/managing-deployment-processes.adoc#deployments-triggers_deployment-operations[Setting deployment resources].
 * xref:../../nodes/nodes/nodes-nodes-resources-configuring.adoc#nodes-nodes-resources-configuring-setting_nodes-nodes-resources-configuring[Allocating resources for nodes].
-endif::openshift-rosa,openshift-dedicated[]
+endif::openshift-rosa,openshift-rosa-classic,openshift-rosa-hcp,openshift-dedicated[]
+ifdef::openshift-rosa,openshift-rosa-classic,openshift-rosa-hcp,openshift-dedicated[]
+* xref:../../support/troubleshooting/sd-managed-resources.adoc#sd-managed-resources[Red Hat Managed resources]
+endif::openshift-rosa,openshift-rosa-classic,openshift-rosa-hcp,openshift-dedicated[]