Version 1.42.12

Fixed issues

When multiple NetScaler Ingress Controllers (NSIC) coexist in a cluster, an NSIC associated with a specific ingress class processes the rewrite policies associated with a different ingress class.
After the NSIC pod restart, if the Kube API fails and is unreachable, NSIC deletes the configuration in NetScaler.
NSIC logs a traceback error when a route is deployed prior to the service mentioned in that route.
The exception handling is faulty in the following scenarios, resulting in an incorrect configuration of metrics server in NetScaler.
- When an NSIC tries to configure a metrics server in NetScaler and the metrics server already exists.
- When multiple NSIC instances try to configure the metrics server in NetScaler simultaneously.
The responder policy parameters, such as redirect-status-code and redirect-reason, are not configured on the corresponding virtual server on NetScaler, even though a responder policy is successfully applied to a service in the Kubernetes cluster.
Sometimes, NSIC fails to update NetScaler based on the updates to Kubernetes’ resource configuration and NetScaler returns an error. In such cases, NSIC clears the existing NetScaler configuration; when the configuration is cleared on NetScaler, an event notification is not logged in Kubernetes.