You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/nap-waf/v5/admin-guide/policy-lifecycle-management.md
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -380,7 +380,7 @@ When Policy Controller is enabled in Helm, the NGINX configuration in your value
380
380
381
381
**For New Installations**: Follow the complete step-by-step process below to install NGINX App Protect WAF with Policy Lifecycle Management enabled.
382
382
383
-
**For Existing Customers**: If you have an existing NGINX App Protect WAF deployment without Policy Lifecycle Management, you need to upgrade your installation to enable PLM functionality. Use `helm upgrade` instead of `helm install` in step 5, and ensure you have the required CRDs and storage configured before upgrading.
383
+
**For Existing Customers**: If you have an existing NGINX App Protect WAF deployment without Policy Lifecycle Management, you need to upgrade your installation to enable PLM functionality. Use `helm upgrade` instead of `helm install` in step 6, and ensure you have the required CRDs and storage configured before upgrading.
384
384
385
385
### Step-by-Step Installation Process
386
386
@@ -417,7 +417,6 @@ When Policy Controller is enabled in Helm, the NGINX configuration in your value
417
417
418
418
3.**Create Storage**
419
419
420
-
Create the directory on the cluster:
421
420
Create the directory on the cluster:
422
421
```bash
423
422
sudo mkdir -p /mnt/nap5_bundles_pv_data
@@ -632,7 +631,7 @@ The APSignatures must have name `signatures`. Only one APSignatures instance can
0 commit comments