Version 2.3.15
What's new
Support to bind preconfigured monitors to Kubernetes backend services
You can now bind preconfigured monitors in NetScaler to Kubernetes services using the existing annotation ingress.citrix.com/monitor
. This enhancement enables you to perform the following actions:
-
Bind the same preconfigured monitor to multiple backend services.
-
Bind a different preconfigured monitor to each backend service.
You can now bind preconfigured monitors in NetScaler to services of type LoadBalancer using the existing service annotation service.citrix.com/monitor
.
For more information, see annotations.
Enhanced security for communication between GSLB sites
For NetScaler GSLB controller deployment, an additional key sitesyncpassword
is supported when creating a secret that GSLB controller uses to connect to GSLB devices and push the configuration. This key enhances the security of communication between the GSLB sites. For more information, see Deploy NetScaler GSLB controller.
Fixed issues
-
The service account token generated in Kubernetes for Kubernetes API authentication expires periodically. As a result, the controller restarts periodically to retrieve the newly generated token for continued authentication.
-
Configuring the default SSL profile
ns_default_ssl_profile_frontend
using the annotationservice.citrix.com/frontend-sslprofile
in services of type LoadBalancer does not bind the default SSL profile to the content switching virtual server. -
GSLB monitor modifications fail intermittently. As a result, changes are not reflected in NetScaler.
-
For NetScaler IPAM controller's integration with Infoblox, when the
reuseIngressVip
parameter is set to true, the same IP address is allocated to resources within a namespace, but a different IP address is allocated to resources in other namespaces.