NetScaler ingress controller

NetScaler Operator release notes

Version 3.1.2

What’s new

Support for GSLB Controller deployment

You can now deploy GSLB Controller using NetScaler Operator. For more information, see Deploy NetScaler GSLB Controller in OpenShift using NetScaler Operator.

Support to configure multiClusterPrefix parameter

You can now configure the multiClusterPrefix parameter in the NetScaler Ingress Controller deployment YAML. For information on how to set up multi-cluster ingress solution, see Multi-cluster ingress.

NetScaler certificate validation in NetScaler Ingress Controller

You can now enable NetScaler certificate validation in NetScaler Ingress Controller. For more information, see Enable NetScaler certificate validation in NetScaler Ingress Controller.

Internet Content Adaptation Protocol (ICAP) support

You can now configure remote content inspection using ICAP.

For more information, see Remote content inspection or content transformation service using ICAP.

Address field of the ingress resource is updated

In an NSIC sidecar deployment, in which NetScaler CPX is exposed using a service of type ClusterIP, NodePort, or LoadBalancer, the Address (Status.LoadBalancer.IP) field of the ingress is updated when you specify updateIngressStatus as true in the deployment YAML.

For more information, see ingress status update for sidecar deployments.

Fixed issues

  • The service account token generated in Azure Kubernetes for Kubernetes API authentication expires every hour. As a result, the controller restarts periodically to retrieve the newly generated token for continued authentication.
NetScaler Operator release notes