Citrix Ingress Controller

NetScaler Ingress Controller connects Kubernetes applications to NetScaler traffic-management systems, formerly branded Citrix ADC. It watches the routing rules declared in Kubernetes and updates a NetScaler appliance or container to send incoming requests to the appropriate services. This is useful when a team already operates NetScaler and wants application routing to follow Kubernetes configuration. The controller configures the traffic-handling system; it is not itself the appliance carrying every request.

Deployment and operating notes

The historical Citrix ADC integration is now documented under NetScaler Ingress Controller. Its upstream repository still describes watching Kubernetes Ingress resources and configuring NetScaler appliances or containerized instances. This is distinct from a standalone generic proxy and should not be confused with the retirement of the Kubernetes community ingress-nginx controller.

Identify whether traffic uses MPX, VPX, CPX or another supported NetScaler form, and record the appliance firmware, controller version, credentials and network topology. Evaluate chart upgrades against the vendor’s compatibility and privilege requirements. Back up appliance configuration and Kubernetes ingress objects before changing ownership or controller settings. Test certificate selection, rewrites, health checks and the network path from the ADC to backends before moving production traffic. A Gateway API plan must account for vendor-specific policies rather than assuming Ingress annotations translate automatically. Keep an independent route to manage the appliance during rollback; a Kubernetes release rollback alone may not restore externally programmed load-balancer configuration.