GHES: Mark Node Eligibility Service as closing down in 3.22 (removal in 3.23) (#61918)

Co-authored-by: Laura Coursen <lecoursen@github.com>
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>

Author: 3 people

content/admin/administering-your-instance/administering-your-instance-from-the-command-line/command-line-utilities.md

@@ -1217,6 +1217,13 @@ ghe-storage evacuate storage-server-UUID
 
 ### nes
 
+{% ifversion ghes > 3.21 %}
+
+> [!IMPORTANT]
+> The `nes` utility and {% data variables.product.prodname_nes %} are closing down and will be removed in {% data variables.product.prodname_ghe_server %} 3.23. There is no replacement.
+
+{% endif %}
+
 This utility allows you to monitor the health of cluster nodes using {% data variables.product.prodname_nes %}. By default, {% data variables.product.prodname_nes %} is disabled. For more information, see [AUTOTITLE](/admin/monitoring-and-managing-your-instance/configuring-clustering/monitoring-the-health-of-your-cluster-nodes-with-node-eligibility-service).
 
 To view the health of the cluster's nodes:

content/admin/monitoring-and-managing-your-instance/configuring-clustering/monitoring-the-health-of-your-cluster-nodes-with-node-eligibility-service.md

@@ -14,6 +14,13 @@ category:
   - Scale your instance
 ---
 
+{% ifversion ghes > 3.21 %}
+
+> [!IMPORTANT]
+> {% data variables.product.prodname_nes %} is closing down and will be removed in {% data variables.product.prodname_ghe_server %} 3.23. There is no replacement. If you have enabled {% data variables.product.prodname_nes %}, you can disable it at any time by running `ghe-config app.nes.enabled false`, followed by `ghe-config-apply`.
+
+{% endif %}
+
 ## About {% data variables.product.prodname_nes %}
 
 In a {% data variables.product.prodname_ghe_server %} cluster, an individual node may become unreachable by other nodes due to a hardware or software failure. After time, even if you restore the node's health, the subsequent synchronization of data can negatively impact your instance's performance.

content/admin/monitoring-and-managing-your-instance/configuring-clustering/monitoring-the-health-of-your-cluster.md

@@ -21,8 +21,6 @@ category:
 
 A {% data variables.product.prodname_ghe_server %} cluster comprises multiple nodes, with redundant services distributed across two or more nodes. If an individual service or an entire node fails, users should not notice. Failures affect performance and redundancy, so it's important to monitor the health of your cluster. You can monitor the health of your cluster using a command-line utility or an external monitoring tool like Nagios.
 
-You can also monitor the health of individual nodes using {% data variables.product.prodname_nes %}. For more information, see [AUTOTITLE](/admin/monitoring-and-managing-your-instance/configuring-clustering/monitoring-the-health-of-your-cluster-nodes-with-node-eligibility-service).
-
 ## Manually checking cluster status
 
 {% data variables.product.prodname_ghe_server %} has a built-in command line utility for monitoring the health of the cluster. From the administrative shell, running the `ghe-cluster-status` command executes a series of health checks on each node including verification of connectivity and service status. The output shows all test results including the text `ok` or `error`. For example, to only display failing tests, run: