About FortiADC Kubernetes Controller
The FortiADC Kubernetes Controller integrates FortiADC’s application delivery and security features with Kubernetes environments. It allows administrators to manage FortiADC virtual servers, real server pools, and GLB directly from Kubernetes by defining either standard Ingress resources or Fortinet’s VirtualServer, RemoteServer, and Host.
Operating as an intermediary between the Kubernetes API and the FortiADC REST API, the controller continuously monitors cluster resources and synchronizes corresponding configurations on FortiADC. When services or pods are added, removed, or updated, the controller automatically reconciles these changes to maintain an accurate, up-to-date application delivery configuration.
Key capabilities include:
-
Automated configuration management — Dynamically maps Kubernetes resources to FortiADC objects, eliminating manual updates.
-
Advanced application delivery — Extends native Kubernetes load balancing with FortiADC features such as SSL offloading, persistence, and Layer 7/Layer 4 content routing.
-
Distributed global traffic — Deploys FortiADC’s Global Load Balance to publish services and direct traffic to suitable servers across different geographical locations.
-
Integrated application security — Applies FortiADC’s Web Application Firewall (WAF), antivirus, and DoS protection to Kubernetes workloads.
-
Operational visibility — Provides unified traffic monitoring and analytics through FortiView and traffic logs.
This document describes the concepts, configuration, and deployment procedures for the FortiADC Kubernetes Controller. It includes information about supported Kubernetes resources, Helm-based installation, configuration parameters, examples of integrating FortiADC with Kubernetes services using Ingress and VirtualServer definitions, and use cases for FortiADC GLB using RemoteServer and Host definitions.