Debug

To see the debug log, you can use the oc logs command.

oc logs -n [namespace] -f [FortiADC Kubernetes Controller pod name]

The log shows which problems you have encountered. For example, the log below shows that you did not have the correct FortiADC Authentication Secret in the OpenShift cluster.

time="2023-04-19T03:22:15Z" level=warning msg="Get fortiadc-login secret failed for fadgw/fad-demo-app: secret \"fad-login2\" not found."
time="2023-04-19T03:22:15Z" level=info msg="Handle updating route fadgw/fad-demo-app done"

Based on the error message, you can correct it and use the oc apply command to reconfigure the Routes.

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

oc -n [namespace] rollout restart deployment/[FortiADC Kubernetes Controller deployment name]