openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

Repaired the links in Introduction to ROSA book

Browse Source
This commit is contained in:
EricPonvelle
2024-09-25 18:04:16 -04:00
parent 8a5cf0c516
commit 95a2299882
11 changed files with 135 additions and 160 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
nodes/index.adoc
View File

@@ -34,13 +34,13 @@ 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.
ifndef::openshift-rosa-hcp,openshift-rosa[]
ifndef::openshift-enterprise,openshift-rosa-hcp,openshift-rosa[]
* 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].
endif::openshift-rosa-hcp,openshift-rosa[]
endif::openshift-enterprise,openshift-rosa-hcp,openshift-rosa[]
ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
ifndef::openshift-enterprise,openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
[discrete]
=== Management operations
@@ -54,7 +54,7 @@ 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-rosa-hcp,openshift-dedicated[]
endif::openshift-enterprise,openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
[discrete]
=== Enhancement operations
@@ -62,16 +62,16 @@ endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
{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.
* Manage node-level tuning for high-performance applications that require some level of kernel tuning by
ifndef::openshift-rosa-hcp,openshift-rosa[]
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].
* 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.
endif::openshift-rosa-hcp,openshift-rosa[]
ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
endif::openshift-enterprise,openshift-rosa-hcp,openshift-rosa[]
ifndef::openshift-enterprise,openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
* Enable TLS security profiles on the node to protect communication between the kubelet and the Kubernetes API server.
* 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-rosa-hcp,openshift-dedicated[]
endif::openshift-enterprise,openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
ifdef::openshift-rosa-hcp,openshift-rosa[]
* link:https://docs.openshift.com/rosa/nodes/jobs/nodes-pods-daemonsets.html#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.
endif::openshift-rosa-hcp,openshift-rosa[]