@@ -889,8 +889,14 @@ status:
889889
890890Check the Policy Controller logs for expected compilation messages :
891891
892+ First, get the Policy Controller pod name :
892893` ` ` bash
893- kubectl logs <policy-controller-pod> -n <namespace> 
894+ kubectl get pods -n <namespace> | grep policy-controller 
895+ ` ` ` 
896+ 
897+ Then check the logs using the pod name from the output above :
898+ ` ` ` bash
899+ kubectl logs <policy-controller-pod-name> -n <namespace> 
894900` ` ` 
895901
896902Look for successful compilation messages like :
@@ -963,12 +969,12 @@ To verify that the policy bundles are being deployed and enforced correctly:
963969
964970   Run the Helm upgrade command to apply the new configuration (replace with your actual release name and namespace) :
965971   ` ` ` bash
966-    helm upgrade <release-name> . --namespace <namespace> --force 
972+    helm upgrade <release-name> . --namespace <namespace> --values /path/to/your/values.yaml -- force 
967973   ` ` `  
968974
969975   Example :
970976   ` ` ` bash
971-    helm upgrade localenv-plm . --namespace localenv-plm --force 
977+    helm upgrade localenv-plm . --namespace localenv-plm --values /path/to/your/values.yaml -- force 
972978   ` ` `  
973979
9749804. **Restart the NGINX Deployment** 
@@ -1142,7 +1148,7 @@ To verify that the policy bundles are being deployed and enforced correctly:
11421148
11431149**Policy Controller Not Starting** 
11441150- Verify CRDs are installed : ` kubectl get crds | grep appprotect.f5.com` 
1145- - Check pod logs : ` kubectl logs < policy-controller-pod>  -n <namespace>` 
1151+ - Check pod logs : ` kubectl logs $(kubectl get pods -n <namespace> -l app= policy-controller -o jsonpath='{.items[0].metadata.name}')  -n <namespace>` 
11461152- Ensure proper RBAC permissions are configured 
11471153
11481154**Policy Compilation Failures** 
0 commit comments