NetScaler GSLB Controller

A Helm chart that deploys the NetScaler GSLB Controller, a Kubernetes controller that provisions and manages Global Server Load Balancing (GSLB) on NetScaler…

  • Infrastructure
  • Tools & Utilities
A Helm chart that deploys the NetScaler GSLB Controller, a Kubernetes controller that provisions and manages Global Server Load Balancing (GSLB) on NetScaler MPX and VPX appliances.

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.

57/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
Security check
75no serious findings

Based on 4 of 5 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 15 days ago - source: GitHub (netscaler/netscaler-helm-charts)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Use a reachable install URL Enter a build file address (URL) that the device can reach, using http, https, sftp, scp, ftp, or file. If it cannot reach that address, the installer cannot download the software and installation stops. source
  • Add a DNS policy for your domains Create a DNS (domain name) policy that matches your domain or client questions and points to a DNS action, the answer the controller should send. Without it, DNS requests are not matched, so your domains will not get the IP answers you want. source
  • Keep 2 GB free for packet capture Before starting nstrace, the packet-capture tool, make sure at least 2 GB of disk space is free. If not, it cannot start, so you cannot inspect traffic to diagnose problems. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can the NetScaler appliance used for GSLB also serve as the Kubernetes ingress appliance?

Yes. A NetScaler MPX or VPX configured as the GSLB appliance can also be used as the ingress appliance with the NetScaler ingress controller.

How is GSLB configuration synchronized across multiple sites?

Use the NetScaler global server load balancing configuration synchronization option. This option is used to synchronize the GSLB configuration across sites.

For a single-site deployment, does the controller need to run in every Kubernetes cluster?

Yes. The single-site procedure deploys the GSLB controller in each cluster. The controllers then configure the NetScaler VPX or MPX to load balance services.

Do IP addresses in GSLB services need to be hosted on the NetScaler?

No. GSLB service IP addresses do not need to be hosted on a Citrix ADC. ADC-owned IP addresses, such as load balancing VIPs, add site persistence options such as cookie-based persistence.

Can a GSLB virtual server marked out of service still deliver traffic?

Yes, in one reported case a NetScaler VPN configured as a GSLB virtual server continued serving traffic even when the virtual server was marked out of service.

Answers sourced from community.stage.citrix.com, docs.netscaler.com, github.com, www.carlstalhood.com

Community

Collected 48 days ago - public community threads