What's new

FortiADC Ingress Controller offers the following new features and enhancements:

2.0.1

• FortiADC Ingress Controller now supports Kubernetes version 1.28.

• Fixed the incorrect content routing HTTP Request URL match condition regex.

2.0.0

OpenShift Container Platform 4 support with Kubernetes Ingress and OpenShift Route

The FortiADC Ingress Controller capability has now been extended to support managing FortiADC objects from RedHat OpenShift Container Platform 4 (OCP 4). FortiADC Ingress Controller can now watch the Kubernetes API for specially formatted OCP 4 Route resources and automatically implement corresponding actions on FortiADC for Add/Update/Delete events.

Support for exposing Kubernetes ClusterIP type services using Ingress

FortiADC Ingress Controller 2.0 now supports ingress to expose services with the ClusterIP type by using Flannel with VXLAN backend as the Kubernetes network model CNI plugin. Since the ClusterIP type Service can only be accessed within the cluster, an overlay-tunnel is required to connect the FortiADC to the Kubernetes cluster network. By using the VXLAN tunnel, FortiADC can forward HTTP/HTTPS requests to the Kubernetes ClusterIP type services.

Note: This feature requires FortiADC 7.4.0 or later to support.

FortiGSLB virtual server configuration support

You can now define the FortiGSLB virtual server configuration in the Kubernetes Ingress and OpenShift Routes annotation.

Added toleration in the FortiADC Ingress Controller Helm deployment template

You can now customize the toleration time to specify how long a pod can remain bound to a node before being evicted. For example, you can specify the amount of time to wait for the FortiADC Ingress Controller to spin up if the Kubernetes node being located becomes unreachable or goes into NotReady state. The default toleration time for in FortiADC Ingress Controller is 30 seconds.