Intel-fpga-initcontainer
Init container that prepares Intel FPGA (Field-Programmable Gate Array) hardware for use in a Kubernetes cluster.
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.
58/100 Fair
- Maintained
- 100last commit 16 days ago
- Popular
- 44152 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- 1048 GB minimum RAM
- GitHub stars
- 152
- Open issues
- 33
- Last commit
- 2026-11-05
- Latest release
- v0.37.1
- License
- Apache-2.0
- Activity
- declining
Checked 16 days ago - source: GitHub (intel/intel-device-plugins-for-kubernetes)
Resources & Compatibility
Minimum requirements: 48 GB RAM. ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Set up NFD before the plugin Run the two kubectl (Kubernetes command-line) commands for NFD (Node Feature Discovery, a helper that labels which hardware each node has) and NodeFeatureRules (label rules). Without those labels, the plugin may not know where to run and apps could start on machines without the hardware. source
- Wait for cert-manager to finish Use the cert-manager Helm (Kubernetes package installer) command with --wait so it pauses until the certificate manager is fully ready. If you continue too early, later Intel components may fail because they cannot get the certificates they need. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
What Node Feature Discovery prerequisite helps the FPGA device plugin target nodes correctly?
Run NFD and NodeFeatureRules before the plugin so nodes receive hardware labels. Without those labels, the plugin may not know where to run and applications could start on machines without FPGA hardware.
What cert-manager installation step can prevent later Intel FPGA components from failing?
Use the cert-manager Helm command with --wait so it pauses until the certificate manager is fully ready. If you continue too early, later Intel components may fail because they cannot get the certificates they need.
Can the Intel device plugin operator currently remove the FPGA init container from a DaemonSet?
No. The NewDaemonSet logic does not set the init container, and UpdateDaemonSet does not support unsetting it properly.
How recent is the published intel-fpga-initcontainer Docker image?
The Docker image page says it was updated over a year ago. It is listed as a verified publisher by Intel Corporation.
Answers sourced from github.com, github.com, github.com, hub.docker.com
Community
Collected 48 days ago - public community threads