Merge branch 'main' into NLB-6773

Author: arpith-f5

.github/workflows/dot-org-content.yml

@@ -9,7 +9,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
     - uses: actions/checkout@v4
-    - uses: actions/setup-node@v4
+    - uses: actions/setup-node@v5
       with:
         node-version: lts/*
     - name: Install dependencies

.github/workflows/playwright.yml

@@ -0,0 +1,88 @@
+---
+title: Features configuration
+weight: 150
+toc: true
+nd-docs: DOCS-000
+nd-content-type: how-to
+---
+
+## Overview
+
+This guide describes the F5 NGINX Agent features, and how to enable and disable features using the NGINX Agent configuration file.
+
+## Before you begin
+
+Before you start, make sure that you have:
+
+- [NGINX Agent installed]({{< ref "/agent/installation-upgrade/" >}}) in your system.
+- Access to the NGINX Agent configuration file.
+
+## Features
+
+The following table lists the NGINX Agent features:
+
+{{< table "features" >}}
+| Feature Name     | Description                                                             | Default/Non-default |
+| ---------------- | ----------------------------------------------------------------------- | ------------------- |
+| registration     | Registering the NGINX Agent with the management plane.                  | Default             |
+| nginx-config-async | Enable the publishing and uploading of NGINX configurations from the management plane. | Default             |
+| metrics          | Enable collecting of NGINX metrics.                                     | Default             |
+| metrics-throttle | Batch metrics before sending.                                           | Non-default         |
+| metrics-sender   | Reports metrics over the gRPC connection.                               | Non-default         |
+| dataplane-status | Report the health of the NGINX Instance.                                | Default             |
+| process-watcher  | Observe changes to the NGINX process.                                   | Default             |
+| file-watcher     | Observe changes to the NGINX configuration or any changes to files on disk. | Default          |
+| activity-events  | Send NGINX or NGINX Agent related events to the management plane.       | Default             |
+| agent-api        | Enable the NGINX Agent REST API.                                        | Default             |
+{{< /table >}}
+
+## Use cases
+
+### Enable metrics only
+
+1. Access the NGINX instance: Connect using SSH to the VM or server where NGINX Agent is running.
+
+   `ssh user@your-nginx-instance`
+
+1. Open the NGINX Agent configuration file in a text editor.
+
+   `sudo vim /etc/nginx-agent/nginx-agent.conf`
+
+1. Add the features section: Add the following to the end of the configuration file if it doesn't already exist.
+
+   ```nginx
+   features:
+      - metrics
+      - metrics-throttle
+      - dataplane-status
+   ```
+
+1. Restart the NGINX Agent service to apply the changes.
+
+   `sudo systemctl restart nginx-agent`
+
+Once the steps have been completed, users will be able to view metrics data being sent but will not have the capability to push NGINX configuration changes.
+
+### Enable the publishing of NGINX configurations and disable the collection of metrics
+
+1. Access the NGINX instance: Connect using SSH to the VM or server where NGINX Agent is running.
+
+   `ssh user@your-nginx-instance`
+
+1. Open the NGINX Agent configuration file in a text editor.
+
+   `sudo vim /etc/nginx-agent/nginx-agent.conf`
+
+1. Add the fetures section: Add the following to the end of the configuration file if it doesn't already exist.
+
+   ```nginx
+   features:
+      - nginx-config-async
+      - dataplane-status
+      - file-watcher
+
+1. Restart the NGINX Agent service to apply the changes.
+
+   `sudo systemctl restart nginx-agent`
+
+Once the steps have been completed, users will be able to publish NGINX configurations but metrics data will not be collected by the NGINX Agent.

content/agent/configuration/configure-nginx-agent-features.md

@@ -8,13 +8,14 @@ files:
 After entering your data plane key, you'll see a `curl` command to install NGINX Agent, similar to the one below. Copy and run this command on each NGINX instance. Once installed, NGINX Agent typically registers with NGINX One within a few seconds.
 
 {{<call-out "important" "Connecting to NGINX One" >}}
- Ensure that any firewall rules you have in place for your NGINX hosts allows network traffic to port `443` for all of the following IPs:
+ Make sure your firewall rules for NGINX hosts allow traffic to port `443` from these IP address ranges:
 
-- `3.135.72.139`
-- `3.133.232.50`
-- `52.14.85.249`
+- `3.135.72.139/32`
+- `3.133.232.50/32`
+- `52.14.85.249/32`
+- `2600:1f16:19c8:d400::/62`
 
-NGINX Agent must be able to establish a connection to NGINX One Console's Agent endpoint (`agent.connect.nginx.com`). 
+NGINX Agent must be able to establish a connection to NGINX One Console's Agent endpoint (`agent.connect.nginx.com`).
 {{</call-out>}}
 
 To install NGINX Agent on an NGINX instance:

content/includes/nginx-one/how-to/install-nginx-agent.md

@@ -413,22 +413,28 @@ When deploying App Protect DoS on NGINX Plus take the following precautions to s
 
 6. Enable Yum repositories to pull NGINX App Protect DoS dependencies:
 
-    If you have a RHEL subscription:
+    For RHEL subscription:
 
     ```shell
     sudo subscription-manager repos --enable=rhel-8-for-x86_64-baseos-rpms
     sudo subscription-manager repos --enable=rhel-8-for-x86_64-appstream-rpms
     sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
     ```
 
-7. Add NGINX Plus and NGINX App Protect DoS repository:
+    For RockyLinux:
+   
+    ```shell
+    sudo dnf -y install epel-release
+    ```
+
+8. Add NGINX Plus and NGINX App Protect DoS repository:
 
     ```shell
     sudo wget -P /etc/yum.repos.d https://cs.nginx.com/static/files/nginx-plus-8.repo
     sudo wget -P /etc/yum.repos.d https://cs.nginx.com/static/files/app-protect-dos-8.repo
     ```
 
-8. In case of fresh installation, update the repository and install the most recent version of the NGINX Plus App Protect DoS package (which includes NGINX Plus):
+9. In case of fresh installation, update the repository and install the most recent version of the NGINX Plus App Protect DoS package (which includes NGINX Plus):
 
     ```shell
     sudo dnf install app-protect-dos
@@ -457,7 +463,7 @@ When deploying App Protect DoS on NGINX Plus take the following precautions to s
     sudo dnf install app-protect-dos-27+2.4.0
     ```
 
-9. In case of upgrading from previously installed NGINX Plus App Protect DoS package (which includes NGINX Plus):
+10. In case of upgrading from previously installed NGINX Plus App Protect DoS package (which includes NGINX Plus):
 
     ```shell
     sudo dnf remove nginx-plus
@@ -621,14 +627,20 @@ When deploying App Protect DoS on NGINX Plus take the following precautions to s
 
 6. Enable the yum repositories to pull NGINX App Protect DoS dependencies:
 
-    If you have a RHEL subscription:
+    For RHEL subscription:
 
     ```shell
     sudo subscription-manager repos --enable=rhel-9-for-x86_64-baseos-rpms
     sudo subscription-manager repos --enable=rhel-9-for-x86_64-appstream-rpms
     sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
     ```
 
+    For RockyLinux:
+   
+    ```shell
+    sudo dnf -y install epel-release
+    ```
+
 7. Add the NGINX Plus and NGINX App Protect DoS repositories:
 
     ```shell