Verifying the Installation
After the deployment is complete, use the following commands to confirm that the FortiADC Kubernetes Controller is installed correctly and operational.
Check Helm Release Status
The helm history command provides the installation status and revision information for your specific release:
helm history -n [Kubernetes NameSpace] [RELEASE_NAME]
Example Output:
user@control-plane-node ~> helm history -n fortiadc-ingress first-release REVISION UPDATED STATUS CHART APP VERSION DESCRIPTION 1 Tue Feb 8 05:37:33 2022 superseded fadc-k8s-ctrl-0.1.0 1.0.0 Install complete
Verify Deployment and Pod Health
Use the kubectl command to ensure the deployment is available and the controller pod is running without restarts:
kubectl get -n [namespace] deployments
kubectl get -n [namespace] pods
Example Output:
user@control-plane-node ~> kubectl get -n fortiadc-ingress deployments NAME READY UP-TO-DATE AVAILABLE AGE first-release-fadc-k8s-ctrl 1/1 1 1 8s
user@control-plane-node ~> kubectl get -n fortiadc-ingress pods NAME READY STATUS RESTARTS AGE first-release-fadc-k8s-ctrl-6447856856-h5skx 1/1 Running 0 8s
Review Controller Logs
Examine the logs to confirm the controller has initialized successfully and is ready to manage traffic:
kubectl logs -n [namespace] -f [pod name]
Expected Log Entry:
user@control-plane-node ~> kubectl logs -n fortiadc-ingress -f \ first-release-fadc-k8s-ctrl-6447856856-h5skx Starting fortiadc ingress controller time=="2021-10-13T06:27:56Z"level=info msg="Starting FortiADC Kubernetes Controller"
Confirm Custom Resource Definition (CRD) Registration
The installation automatically installs the VirtualServer, RemoteServer, and Host CRDs. These extend the Kubernetes API to support advanced FortiADC configurations. Verify they are applied using the following command:
kubectl get crds
Expected Results:
NAME CREATED AT virtualservers.fadk8sctrl.fortinet.com 2025-11-19T02:21:52Z hosts.fadk8sctrl.fortinet.com 2025-11-19T02:21:52Z remoteservers.fadk8sctrl.fortinet.com 2025-11-19T02:21:52Z