This release note contains information about the changes for the NetScaler Node Controller (NSNC), formerly known as Citrix Node Controller, version 2.2.12.

What's new

Optimized size of the NSNC image

The new version of the NetScaler Node Controller (NSNC) is notably more streamlined, resulting in significantly reduced resource consumption compared to its previous iterations.

What's fixed

Avoiding unwarranted creation of the kube-router pods

Previously, any update made to the Citrix-node-controller configmap would trigger the deletion and subsequent recreation of the kube-router pods, even if the data in the configmap remained unaltered. This issue has now been addressed, ensuring that the router pods are only recreated in response to modifications made to the configmap data, thereby significantly reducing unnecessary recreation events.

Wrongful termination of the router pod by another instance of the NSNC

Earlier if multiple instances of the NSNC were made on the same Kubernetes cluster and one instance's name was part of another instance's name, then it was possible that one NSNC wrongfully terminates the router pods created by the other NSNC. This issue is fixed now.

Sanitization of the logs

All log messages within the NSNC are thoroughly sanitized to ensure that no sensitive information is displayed ensuring the stringent data privacy and security protocols.

This release note contains information about the changes for the Citrix node controller version 2.2.11.

What's new

Toleration support

Citrix node controller now supports providing tolerations for kube-cnc-router and node-controller pods so that you can schedule them on appropriate tainted nodes. The tolerations shoud be specificied in the ConfigMap.

This release note contains information about the changes for the Citrix node controller version 2.2.10.

What’s New

• An optional environment variable CNC_CONFIGMAP is added for specifying the name of the ConfigMap that the Citrix node controller watches for configuration settings. For more information, see Citrix node controller GitHub repository.

• An optional environment variable CNC_ROUTER_NAME is added for specifying the RBAC, service account, ConfigMap name, and pod prefix for kube-cnc-router helper pods. If the CNC_Router_Name variable is not specified, kube-cnc-router values are used by default. For more information, see Citrix node controller GitHub repository.

Fixed issues

• OVN CNI is now supported.

Fixed Issues

• Earlier, when you use the Weave CNI and a worker node is removed all routes were getting deleted. This issue is fixed now.
• The value of theCNI_TYPE environment variable that specifies the CNI used in the Kubernetes cluster is now case-insensitve. Earlier it was case-sensitive.

Fixed issues

• Router pods were getting created even when the user provides wrong credentials to access Citrix ADC. This issue is fixed now.
• Improved exception handling if there is a wrong user input or unauthorised Citrix ADC access

Fixed issues

• New nodes were not getting added when Citrix node controller receives only one Ready event and do not receive a Taint Removal event afterwards. This issue is fixed now.
• Log improvements are implemented for better debugging.

Release Note for Citrix Node Controller version 2.2.5

Fixed Issues

• Earlier, when a node running Citrix node controller is rebooted, multiple route entries were getting added for the same host. This issue is now fixed.
• Log improvements are implemented for better debugging.

Version 2.2.4

What's new

• An optional environment variable CNC_ROUTER_IMAGE is introduced for Citrix node controller. The CNC_ROUTER_IMAGE environment variable is used to access the kube-cnc-router helper pod's image from the internal repository when the Kubernetes cluster nodes do not have internet access. For more information, see [Running Citrix node controller without Internet access] (https://github.com/citrix/citrix-k8s-node-controller/blob/master/deploy/README.md#running-citrix-node-controller-without-internet-access)
• The NS_IP environment variable now accepts host name along with the IP address of Citrix ADC.

Version 2.2.3

What's new

An optional environment variable CLUSTER_NAME is added for PolicyBasedRoutes(PBR) support in Citrix Node Controller.

Now, the Citrix ADC can be configured with PolicyBasedRoutes Instead of static routes in the multi-cluster scenario. For more details refer to CNC-PBR-SUPPORT

Fixed Issues

Earlier, IP addresses in the CNC network pool were getting exhausted when router pods restart frequently. This issue is now fixed.