Skip to content

Commit 61c3c2b

Browse files
authored
Merge branch 'main' into NLB-6773
2 parents 45b256c + b583969 commit 61c3c2b

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

41 files changed

+1510
-275
lines changed

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

Lines changed: 0 additions & 56 deletions
This file was deleted.

.github/workflows/playwright.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ jobs:
99
runs-on: ubuntu-latest
1010
steps:
1111
- uses: actions/checkout@v4
12-
- uses: actions/setup-node@v4
12+
- uses: actions/setup-node@v5
1313
with:
1414
node-version: lts/*
1515
- name: Install dependencies

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

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,13 +8,14 @@ files:
88
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.
99

1010
{{<call-out "important" "Connecting to NGINX One" >}}
11-
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:
11+
Make sure your firewall rules for NGINX hosts allow traffic to port `443` from these IP address ranges:
1212

13-
- `3.135.72.139`
14-
- `3.133.232.50`
15-
- `52.14.85.249`
13+
- `3.135.72.139/32`
14+
- `3.133.232.50/32`
15+
- `52.14.85.249/32`
16+
- `2600:1f16:19c8:d400::/62`
1617

17-
NGINX Agent must be able to establish a connection to NGINX One Console's Agent endpoint (`agent.connect.nginx.com`).
18+
NGINX Agent must be able to establish a connection to NGINX One Console's Agent endpoint (`agent.connect.nginx.com`).
1819
{{</call-out>}}
1920

2021
To install NGINX Agent on an NGINX instance:

content/nap-dos/deployment-guide/learn-about-deployment.md

Lines changed: 17 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -413,22 +413,28 @@ When deploying App Protect DoS on NGINX Plus take the following precautions to s
413413
414414
6. Enable Yum repositories to pull NGINX App Protect DoS dependencies:
415415
416-
If you have a RHEL subscription:
416+
For RHEL subscription:
417417
418418
```shell
419419
sudo subscription-manager repos --enable=rhel-8-for-x86_64-baseos-rpms
420420
sudo subscription-manager repos --enable=rhel-8-for-x86_64-appstream-rpms
421421
sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
422422
```
423423
424-
7. Add NGINX Plus and NGINX App Protect DoS repository:
424+
For RockyLinux:
425+
426+
```shell
427+
sudo dnf -y install epel-release
428+
```
429+
430+
8. Add NGINX Plus and NGINX App Protect DoS repository:
425431
426432
```shell
427433
sudo wget -P /etc/yum.repos.d https://cs.nginx.com/static/files/nginx-plus-8.repo
428434
sudo wget -P /etc/yum.repos.d https://cs.nginx.com/static/files/app-protect-dos-8.repo
429435
```
430436
431-
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):
437+
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):
432438
433439
```shell
434440
sudo dnf install app-protect-dos
@@ -457,7 +463,7 @@ When deploying App Protect DoS on NGINX Plus take the following precautions to s
457463
sudo dnf install app-protect-dos-27+2.4.0
458464
```
459465
460-
9. In case of upgrading from previously installed NGINX Plus App Protect DoS package (which includes NGINX Plus):
466+
10. In case of upgrading from previously installed NGINX Plus App Protect DoS package (which includes NGINX Plus):
461467
462468
```shell
463469
sudo dnf remove nginx-plus
@@ -621,14 +627,20 @@ When deploying App Protect DoS on NGINX Plus take the following precautions to s
621627
622628
6. Enable the yum repositories to pull NGINX App Protect DoS dependencies:
623629
624-
If you have a RHEL subscription:
630+
For RHEL subscription:
625631
626632
```shell
627633
sudo subscription-manager repos --enable=rhel-9-for-x86_64-baseos-rpms
628634
sudo subscription-manager repos --enable=rhel-9-for-x86_64-appstream-rpms
629635
sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
630636
```
631637
638+
For RockyLinux:
639+
640+
```shell
641+
sudo dnf -y install epel-release
642+
```
643+
632644
7. Add the NGINX Plus and NGINX App Protect DoS repositories:
633645
634646
```shell

content/nap-waf/v5/admin-guide/overview.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -66,6 +66,14 @@ Use the [NGINX App Protect WAF Compiler]({{< ref "/nap-waf/v5/admin-guide/compil
6666

6767
For signature updates, read the [Update App Protect Signatures]({{< ref "/nap-waf/v5/admin-guide/compiler.md#update-app-protect-signatures" >}}) section of the compiler documentation.
6868

69+
## Policy Lifecycle Management
70+
71+
NGINX App Protect WAF v5 introduces Policy Lifecycle Management (PLM) as a comprehensive solution for automating the management, compilation, and deployment of security policies within Kubernetes environments. PLM extends the WAF compiler capabilities by providing a native Kubernetes operator-based approach to policy orchestration.
72+
73+
The Policy Lifecycle Management system is architected around a **Policy Controller** that implements the Kubernetes operator pattern to manage the complete lifecycle of WAF security artifacts. The system addresses the fundamental challenge of policy distribution at scale by eliminating manual intervention points and providing a declarative configuration model through Custom Resource Definitions (CRDs) for policies, logging profiles, signatures, and user-defined signatures.
74+
75+
For detailed information about PLM architecture, functional components, and deployment procedures, see [Policy Lifecycle Management Guide]({{< ref "/nap-waf/v5/admin-guide/policy-lifecycle-management.md" >}}).
76+
6977
---
7078

7179
## Transitioning from NGINX App Protect WAF v4 to v5

0 commit comments

Comments
 (0)