The common deployment architectures emerging in K8s environment are of single-tier and dual-tier load balancing.
Netscaler with Ingress Controller provides solution for these deployments. The Netscaler ingress controller automates the configuration of Netscaler load balancing microservices in Kubernetes environment.
North-South traffic Load balancing: North-South traffic is the traffic heading in and out of your Kubernetes Cluster. It is the traffic that comes from the client and hits the frontend microservices.
East-West traffic Load balancing: East-West traffic is the traffic from one microservice to another inside the Kubernetes Cluster.
In usual k8s environment the E-W traffic is load balanced by kube-proxy and N-S traffic is load balanced by Ingress load balancer like Netscaler.
The E-W traffic can also be load balanced by Ingress load balancer with E-W Hairpin mode.
- Ingress Class
- Ingress Configuration
- TCP Ingress
- Annotations
- Network configuration:
- Automated Certificate Management with cert-manager
- HTTP, TCP, or SSL Profiles support
- TLS Certificate Handling
- Install, link, and update certificates on Netscaler using the Netscaler ingress controller
- Rewrite and Responder
- Advanced content routing
- Canary deployment support
- Rate limiting
- Authentication policies
- OpenShift router plug-in
- Openshift router sharding support