Fortiadc-ingress
FortiADC Ingress is a Kubernetes ingress controller that syncs standard Kubernetes Ingress and Gateway API resources to a Fortinet FortiADC application…
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
41/100 Fair
- Maintained
- 68last commit 74 days ago
- Popular
- 187 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- 304 GB minimum RAM
- GitHub stars
- 7
- Open issues
- 5
- Last commit
- 2026-09-08
- License
- Apache-2.0
- Activity
- stale
Checked yesterday - source: GitHub (fortinet/fortiadc-kubernetes-controller)
Resources & Compatibility
Minimum requirements: 4 GB RAM, 2 CPU core(s). ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Install the FortiADC Ansible collection first Before your first run, install the collection on the machine that runs Ansible. If it is missing, Ansible cannot find the FortiADC task modules and the automation stops immediately. source
- Create a virtual server with the right port and pool Add the virtual server with the IP, port, server pool (the back-end servers that handle traffic), and HTTPS/SSL profile before expecting connections. If any of these are missing or wrong, users may not reach the site or secure connections can fail. source
- Set VDOM only if your FortiADC uses it Use the `vdom` parameter when your FortiADC is divided into VDOMs (separate virtual domains). If VDOM is disabled, omit it; otherwise tasks can fail or target the wrong domain. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Why does creating an Ingress resource alone not expose my service?
An Ingress controller must be present to satisfy the Ingress. FortiADC Kubernetes Controller fulfills Ingress resources only when they use the IngressClass fadc-ingress-controller.
Which Kubernetes Ingress API group should I use?
Disable the extensions/v1beta1 API group if it is enabled. This ensures the system uses networking.k8s.io/v1, which is supported by FortiADC Ingress Controller.
What FortiADC virtual server details must be set before traffic should arrive?
Create the virtual server with the correct IP, port, server pool, and HTTPS/SSL profile. Missing or wrong values can prevent users from reaching the site or cause secure connections to fail.
When should I specify a VDOM in FortiADC API tasks?
Set the vdom parameter only when your FortiADC uses VDOMs. If VDOM is disabled, omit it to avoid task failure or targeting the wrong domain.
Answers sourced from docs.fortinet.com, docs.fortinet.com, github.com, github.com
Community
- Anyone use Fortinet at home? : r/fortinet - Reddit (reddit)
- Fortinet Discussion Forum (other)
- Knowledge base | Community (other)
- FYI: "Fortinet Technical Discussion Forums" become the ... - Reddit (reddit)
- Those of you using wireguard for ingress : r/selfhosted - Reddit (reddit)
Collected 29 days ago - public community threads