Debug

By default, the FortiWeb Ingress Controller records the process of the Ingress implementation in verbose mode. The debug log shows the check of annotation parameters and the process of calling the REST API to FortiWeb when deploying, updating, or deleting the Ingress resources.

The verbose log can be enabled or disabled for any particular Ingress. This is determined by the status of the FortiWeb-ctrl-log configuration parameter. For more information, see Configuration parameters.

To see the log, you can use the kubectl logs command:

kubectl logs -n [namespace] -f [FortiWeb Ingress Controller pod name] 

The log shows which problem you encounter.

Some troubleshooting steps may require restarting the FortiWeb Ingress Controller. For example, the FortiWeb Ingress Controller may not connect to FortiWeb after changing the network firewall rule. To fix this type of environment issue, you can restart the FortiWeb Ingress Controller by using the following command:

kubectl -n [namespace] rollout restart deployment/[ FortiWeb Ingress Controller deployment name]