Skip to content

Commit 14b40ee

Browse files
committed
fix: after rebase
1 parent c2200de commit 14b40ee

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

content/nap-waf/v5/admin-guide/policy-lifecycle-management.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -380,7 +380,7 @@ When Policy Controller is enabled in Helm, the NGINX configuration in your value
380380

381381
**For New Installations**: Follow the complete step-by-step process below to install NGINX App Protect WAF with Policy Lifecycle Management enabled.
382382

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.
384384

385385
### Step-by-Step Installation Process
386386

@@ -417,7 +417,6 @@ When Policy Controller is enabled in Helm, the NGINX configuration in your value
417417

418418
3. **Create Storage**
419419

420-
Create the directory on the cluster:
421420
Create the directory on the cluster:
422421
```bash
423422
sudo mkdir -p /mnt/nap5_bundles_pv_data
@@ -632,7 +631,7 @@ The APSignatures must have name `signatures`. Only one APSignatures instance can
632631
Apply the manifest:
633632

634633
```bash
635-
kubectl apply -f config/policy-manager/samples/appprotect_v1_apsignatures.yaml
634+
kubectl apply -f signatures.yaml -n <namespace>
636635
```
637636

638637
{{< call-out "note" >}}
@@ -689,7 +688,6 @@ spec:
689688
```
690689

691690
Apply the policy:
692-
693691
```bash
694692
kubectl apply -f dataguard-blocking-policy.yaml -n <namespace>
695693
```
@@ -724,7 +722,6 @@ spec:
724722
```
725723

726724
Apply the user signature:
727-
728725
```bash
729726
kubectl apply -f apple-usersig.yaml -n <namespace>
730727
```
@@ -1017,7 +1014,7 @@ To verify that the policy bundles are being deployed and enforced correctly:
10171014
```bash
10181015
curl "http://<CLUSTER-IP>:80/680-15-0817"
10191016
```
1020-
1017+
10211018
Example:
10221019
```bash
10231020
curl "http://10.43.205.101:80/680-15-0817"
@@ -1126,6 +1123,7 @@ To verify that the policy bundles are being deployed and enforced correctly:
11261123
--set appprotect.nginxRepo.nginxCrt=$NGINX_CERT \
11271124
--set appprotect.nginxRepo.nginxKey=$NGINX_KEY
11281125
```
1126+
11291127
8. **Verify Upgrade**
11301128

11311129
Check that all components are deployed successfully:
@@ -1162,6 +1160,7 @@ To verify that the policy bundles are being deployed and enforced correctly:
11621160
kubectl delete crd --all
11631161
kubectl delete ns <namespace>
11641162
```
1163+
11651164
## Troubleshooting
11661165

11671166
### Common Issues

0 commit comments

Comments
 (0)