NetScaler CPX with Ingress Controller
A Helm chart for NetScaler CPX with NetScaler ingress Controller running as sidecar.
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- 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.
53/100 Fair
- Maintained
- 82last commit 19 days ago
- Popular
- 2928 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today
- GitHub stars
- 28
- Open issues
- 5
- Last commit
- 2026-11-02
- Latest release
- nsnc-v3.2.13
- License
- Apache-2.0
- Activity
- declining
Checked 14 days ago - source: GitHub (netscaler/netscaler-helm-charts)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Point the install command to a real file URL Use the install command's url argument to point at the .tgz package (http, https, sftp, scp, ftp, or a local file path). If the URL is missing or invalid, the installer can't find the software and the install fails. source
- Leave room for packet capture If you run nstrace (a tool that records network traffic) to check connections, make sure at least 2 GB of disk space is free first. Otherwise the trace can't start. source
Fetched 41 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
If I already run a NetScaler controller in front of the cluster, what should I configure?
Use the existing NetScaler instead of having the chart deploy CPX. Leave useNetscalerController off and set ingressClass to the class used by your existing controller.
When the ingress controller runs as a sidecar, which NetScaler does it configure?
It is only responsible for the NetScaler CPX that resides in the same pod.
Does the NetScaler CPX chart apply profiles that avoid idle-connection disconnects?
Yes. The chart applies the right profiles itself for NetScaler CPX, while aggressive idle closing or response buffering can otherwise produce disconnects that look like platform faults.
Where can I find deployment-specific CPX discussions?
There is a Citrix community forum section for deployment-specific discussions about NetScaler VPX, CPX, and BLX.
Answers sourced from community.citrix.com, docs.citrix.com, docs.citrix.com, docs.netscaler.com
Community
- NetScaler - Citrix Community (other)
- NetScaler Platforms - Software (VPX, CPX, BLX) - Citrix Community (other)
Collected 48 days ago - public community threads