ROSA with HCP split integration

nodes/index.adoc

@@ -34,11 +34,18 @@ image::295_OpenShift_Nodes_Overview_1222.png[Overview of control plane and worke
 
 The read operations allow an administrator or a developer to get information about nodes in an {product-title} cluster.
 
+ifdef::openshift-rosa-hcp[]
+* List all the nodes in a cluster.
+* Get information about a node, such as memory and CPU usage, health, status, and age.
+* List pods running on a node.
+ifndef::openshift-rosa-hcp[]
+ifndef::openshift-rosa-hcp[]
 * xref:../nodes/nodes/nodes-nodes-viewing.adoc#nodes-nodes-viewing-listing_nodes-nodes-viewing[List all the nodes in a cluster].
 * Get information about a node, such as memory and CPU usage, health, status, and age.
 * xref:../nodes/nodes/nodes-nodes-viewing.adoc#nodes-nodes-viewing-listing-pods_nodes-nodes-viewing[List pods running on a node].
+ifndef::openshift-rosa-hcp[]
 
-ifndef::openshift-rosa,openshift-dedicated[]
+ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 [discrete]
 === Management operations
 
@@ -52,28 +59,36 @@ through several tasks:
 * xref:../nodes/nodes/nodes-nodes-managing-max-pods.adoc#nodes-nodes-managing-max-pods-proc_nodes-nodes-managing-max-pods[Configure the number of pods that can run on a node] based on the number of processor cores on the node, a hard limit, or both.
 * Reboot a node gracefully using xref:../nodes/nodes/nodes-nodes-rebooting.adoc#nodes-nodes-rebooting-affinity_nodes-nodes-rebooting[pod anti-affinity].
 * xref:../nodes/nodes/nodes-nodes-working.adoc#deleting-nodes[Delete a node from a cluster] by scaling down the cluster using a compute machine set. To delete a node from a bare-metal cluster, you must first drain all pods on the node and then manually delete the node.
-endif::openshift-rosa,openshift-dedicated[]
+endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 
 [discrete]
 === Enhancement operations
 
 {product-title} allows you to do more than just access and manage nodes; as an administrator, you can perform the following tasks on nodes to make the cluster more efficient, application-friendly, and to provide a better environment for your developers.
 
+ifndef::openshift-rosa-hcp[]
+* Manage node-level tuning for high-performance applications that require some level of kernel tuning by using the Node Tuning Operator.
+* Run background tasks on nodes automatically with daemon sets. You can create and use daemon sets to create shared storage, run a logging pod on every node, or deploy a monitoring agent on all nodes.
+endif::openshift-rosa-hcp[]
+ifndef::openshift-rosa-hcp[]
 * Manage node-level tuning for high-performance applications that require some level of kernel tuning by xref:../nodes/nodes/nodes-node-tuning-operator.adoc#nodes-node-tuning-operator[using the Node Tuning Operator].
 ifndef::openshift-rosa,openshift-dedicated[]
-=======
-ifndef::openshift-enterprise,openshift-rosa-hcp,openshift-rosa[]
-xref:../nodes/nodes/nodes-node-tuning-operator.adoc#nodes-node-tuning-operator[using the Node Tuning Operator].
+* Enable TLS security profiles on the node to protect communication between the kubelet and the Kubernetes API server.
+endif::openshift-rosa,openshift-dedicated[]
+* xref:../nodes/jobs/nodes-pods-daemonsets.adoc#nodes-pods-daemonsets[Run background tasks on nodes automatically with daemon sets]. You can create and use daemon sets to create shared storage, run a logging pod on every node, or deploy a monitoring agent on all nodes.
+ifndef::openshift-rosa,openshift-dedicated[]
 * xref:../nodes/nodes/nodes-nodes-garbage-collection.adoc#nodes-nodes-garbage-collection[Free node resources using garbage collection]. You can ensure that your nodes are running efficiently by removing terminated containers and the images not referenced by any running pods.
 * xref:../nodes/nodes/nodes-nodes-managing.adoc#nodes-nodes-kernel-arguments_nodes-nodes-managing[Add kernel arguments to a set of nodes].
 * Configure an {product-title} cluster to have worker nodes at the network edge (remote worker nodes). For information on the challenges of having remote worker nodes in an {product-title} cluster and some recommended approaches for managing pods on a remote worker node, see xref:../nodes/edge/nodes-edge-remote-workers.adoc#nodes-edge-remote-workers[Using remote worker nodes at the network edge].
 endif::openshift-rosa,openshift-dedicated[]
+endif::openshift-rosa-hcp[]
 
 [id="pods-overview"]
 == About pods
 
 A pod is one or more containers deployed together on a node. As a cluster administrator, you can define a pod, assign it to run on a healthy node that is ready for scheduling, and manage. A pod runs as long as the containers are running. You cannot change a pod once it is defined and is running. Some operations you can perform when working with pods are:
 
+ifndef::openshift-rosa-hcp[]
 [discrete]
 === Read operations
 
@@ -81,12 +96,23 @@ As an administrator, you can get information about pods in a project through the
 
 * xref:../nodes/pods/nodes-pods-viewing.adoc#nodes-pods-viewing-project_nodes-pods-viewing[List pods associated with a project], including information such as the number of replicas and restarts, current status, and age.
 * xref:../nodes/pods/nodes-pods-viewing.adoc#nodes-pods-viewing-usage_nodes-pods-viewing[View pod usage statistics] such as CPU, memory, and storage consumption.
+endif::openshift-rosa-hcp[]
 
 [discrete]
 === Management operations
 
 The following list of tasks provides an overview of how an administrator can manage pods in an {product-title} cluster.
 
+ifdef::openshift-rosa-hcp[]
+* Control scheduling of pods using the advanced scheduling features available in {product-title}:
+** Node-to-pod binding rules such as pod affinity, node affinity, and anti-affinity.
+** Node labels and selectors.
+** Pod topology spread constraints.
+* Configure how pods behave after a restart using pod controllers and restart policies.
+* Limit both egress and ingress traffic on a pod.
+* Add and remove volumes to and from any object that has a pod template. A volume is a mounted file system available to all the containers in a pod. Container storage is ephemeral; you can use volumes to persist container data.
+endif::openshift-rosa-hcp[]
+ifndef::openshift-rosa-hcp[]
 * Control scheduling of pods using the advanced scheduling features available in {product-title}:
 ** Node-to-pod binding rules such as xref:../nodes/scheduling/nodes-scheduler-pod-affinity.adoc#nodes-scheduler-pod-affinity-example-affinity_nodes-scheduler-pod-affinity[pod affinity], xref:../nodes/scheduling/nodes-scheduler-node-affinity.adoc#nodes-scheduler-node-affinity[node affinity], and xref:../nodes/scheduling/nodes-scheduler-pod-affinity.adoc#nodes-scheduler-pod-anti-affinity-configuring_nodes-scheduler-pod-affinity[anti-affinity].
 ** xref:../nodes/scheduling/nodes-scheduler-node-selectors.adoc#nodes-scheduler-node-selectors[Node labels and selectors].
@@ -102,13 +128,14 @@ endif::openshift-rosa,openshift-dedicated[]
 * xref:../nodes/pods/nodes-pods-configuring.adoc#nodes-pods-configuring-restart_nodes-pods-configuring[Configure how pods behave after a restart using pod controllers and restart policies].
 * xref:../nodes/pods/nodes-pods-configuring.adoc#nodes-pods-configuring-bandwidth_nodes-pods-configuring[Limit both egress and ingress traffic on a pod].
 * xref:../nodes/containers/nodes-containers-volumes.adoc#nodes-containers-volumes[Add and remove volumes to and from any object that has a pod template]. A volume is a mounted file system available to all the containers in a pod. Container storage is ephemeral; you can use volumes to persist container data.
+endif::openshift-rosa-hcp[]
 
 [discrete]
 === Enhancement operations
 
 You can work with pods more easily and efficiently with the help of various tools and features available in {product-title}. The following operations involve using those tools and features to better manage pods.
 
-ifndef::openshift-rosa,openshift-dedicated[]
+ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 [cols="2,1,2"]
 |===
 |Operation |User |More information
@@ -133,7 +160,7 @@ As a developer, use a vertical pod autoscaler to ensure your pods stay up during
 
 
 |===
-endif::openshift-rosa,openshift-dedicated[]
+endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 ifdef::openshift-rosa,openshift-dedicated[]
 * Secrets: Some applications need sensitive information, such as passwords and usernames. An administrator can use the `Secret` object to provide sensitive data to pods xref:../nodes/pods/nodes-pods-secrets.adoc#nodes-pods-secrets[using the `Secret` object].
 endif::openshift-rosa,openshift-dedicated[]
@@ -143,6 +170,18 @@ endif::openshift-rosa,openshift-dedicated[]
 
 A container is the basic unit of an {product-title} application, which comprises the application code packaged along with its dependencies, libraries, and binaries. Containers provide consistency across environments and multiple deployment targets: physical servers, virtual machines (VMs), and private or public cloud.
 
+ifdef::openshift-rosa-hcp[]
+Linux container technologies are lightweight mechanisms for isolating running processes and limiting access to only designated resources.
+As an administrator, You can perform various tasks on a Linux container, such as:
+
+* Copy files to and from a container.
+* Allow containers to consume API objects.
+* Execute remote commands in a container.
+* Use port forwarding to access applications in a container.
+
+{product-title} provides specialized containers called Init containers. Init containers run before application containers and can contain utilities or setup scripts not present in an application image. You can use an Init container to perform tasks before the rest of a pod is deployed.
+endif::openshift-rosa-hcp[]
+ifndef::openshift-rosa-hcp[]
 Linux container technologies are lightweight mechanisms for isolating running processes and limiting access to only designated resources.
 As an administrator, You can perform various tasks on a Linux container, such as:
 
@@ -152,12 +191,13 @@ As an administrator, You can perform various tasks on a Linux container, such as
 * xref:../nodes/containers/nodes-containers-port-forwarding.adoc#nodes-containers-port-forwarding[Use port forwarding to access applications in a container].
 
 {product-title} provides specialized containers called xref:../nodes/containers/nodes-containers-init.adoc#nodes-containers-init[Init containers]. Init containers run before application containers and can contain utilities or setup scripts not present in an application image. You can use an Init container to perform tasks before the rest of a pod is deployed.
+endif::openshift-rosa-hcp[]
 
 Apart from performing specific tasks on nodes, pods, and containers, you can work with the overall {product-title} cluster to keep the cluster efficient and the application pods highly available.
 
 
 //cannot create the required namespace for these operators
-ifndef::openshift-rosa,openshift-dedicated[]
+ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 [id="nodes-about-autoscaling-pod_{context}"]
 == About autoscaling pods on a node
 
@@ -177,7 +217,7 @@ Vertical Pod Autoscaler::
 The Vertical Pod Autoscaler (VPA) can automatically review the historic and current CPU and memory resources for containers in pods and can update the resource limits and requests based on the usage values it learns.
 +
 For more information, see xref:../nodes/pods/nodes-pods-vertical-autoscaler.adoc#nodes-pods-vpa[Automatically adjust pod resource levels with the vertical pod autoscaler].
-endif::openshift-rosa,openshift-dedicated[]
+endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 
 [id="commonterms-node"]
 == Glossary of common terms for {product-title} nodes