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.
What you can do with NetScaler for Kubernetes multi-cluster routing
Use NetScaler Ingress Controller to automate the configuration of NetScaler ADCs to proxy traffic into your Kubernetes clusters
Apply the same configurations across containerized and non-containerized NetScaler ADCs
Manage and secure north-south and east-west traffic
Automatically route traffic to the best cluster based on load and availability
Use NetScaler features like WAF, routing, and content rewrite and responder at the container group level
Use NetScaler for Kubernetes with tools you already use like Red Hat OpenShift, Rancher, and Pivotal Container Service
Setting up Kubernetes multi-cluster routing
NetScaler for Kubernetes multi-cluster routing at a glance
NetScaler Ingress Controller
NetScaler Ingress Controller integrates with the NetScaler API gateway so you can expose your APIs outside the Kubernetes cluster faster without worrying about compliance and security
NetScaler API gateway is purpose built to integrate seamlessly into a Kubernetes environment by leveraging GitOps, an operational framework for DevOps best practices for application development
Configuring multi-cluster Kubernetes ingress with NetScaler GSLB provides a multi-cluster Kubernetes ingress and load balancing solution that monitors applications, collects and shares metrics across multiple clusters, and automates intelligent load balancing
For faster troubleshooting in Kubernetes clusters, NetScaler provides service graphs that monitor services within a Kubernetes cluster by using the four golden signals (latency, traffic, errors, and saturation) along with P99 data to provide information about the pod or pods so you can pinpoint down to the individual microservice where a given issue lies
ML-based threat detection provides an advanced early-warning system to surface the “unknown unknowns” so that you can take immediate proactive action