Release 3.2.22

Release 3.2.22

Fixed Issues

• Creating a content switching virtual server can fail due to issues, such as IP address conflicts. When the NetScaler Ingress Controller attempts to bind certificates and policies to a non-existent virtual server, there are misleading, cascading errors in the logs.
• The NetScaler Ingress Controller creates a new SSL profile, overriding the preconfigured SSL profiles provided in the listener instance. This issue occurs when both of the following conditions are met:
  • A preconfigured SSL profile exists in the listener
  • The default SSL SNI certificate is used in the NetScaler Ingress Controller
• With each ingress creation, the NetScaler Ingress Controller deletes the existing SSL profile and creates an SSL profile instead of reusing the existing profile. This change impacts the traffic flow as the status of the SSL content switching virtual server changes from UP to DOWN and then UP again.
• When the NetScaler Ingress Controller receives a virtual IP (VIP) address with an incorrect format, it throws an error but continues to process the remaining configuration. The invalid VIP address prevents the initial creation of the content switching virtual server (CSVS), leading to numerous subsequent errors.
• If an HTTP route that references the same backend service multiple times exists in the cluster before deploying the NetScaler Ingress Controller or NetScaler Kubernetes Gateway Controller, some of the routing rules for that service are missed in the NetScaler configuration.
• During reconciliation of configurations by NetScaler Ingress Controller, the rewrite responder policy bindings for HTTPRoute configuration might get deleted and then added back.