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.