If you already use NetScaler ADCs in your on-premises environments, you can use the same ADCs for your Kubernetes environments to apply the same load balancing and Layer 7 policies to your microservices in Kubernetes clusters.

NetScaler Ingress Controller, which works alongside the NetScaler multi-cluster ingress controller, automates the configuration of NetScaler ADCs to proxy traffic into your Kubernetes clusters for failover and canary deployment and to reduce round-trip time.

The NetScaler multi-cluster ingress controller features a Kubernetes-native UI (that uses kubectl) to help you more easily manage applications deployed across multiple clusters, Additionally, you can use custom resource definitions (CRDs) to configure global server load balancing (GSLB) on your NetScaler ADCs to ensure better performance and reliability. The NetScaler multi-cluster ingress controller uses GSLB to send traffic to the best cluster based on load and availability for any Kubernetes service exposed outside the cluster.