Skip to content

Helm chart release notes for NetScaler Ingress Controller version 1.39.6
Compare
Choose a tag to compare
@subashd subashd released this 23 Feb 09:39
· 16 commits to master since this release
nsic-v1.39.6
56a71a6
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

This release note contains information about the Helm chart-related changes for the NetScaler Ingress and GSLB Controller version 1.39.6.

What’s New

Enhanced Security Posture

In our ongoing commitment to security and reliability, this release introduces a significant upgrade to the NetScaler Ingress Controller (NSIC). We have transitioned to a new underlying base image, meticulously selected and optimized to ensure that all installed packages are patched against known Common Vulnerabilities and Exposures (CVEs). This strategic update bolsters the security framework of the NSIC.

Compatibility with OVN CNI-based OpenShift v4.13+ environments

This release addresses and resolves a previously identified issue affecting the NSIC when operating on OpenShift v4.13 with the OVN CNI. The OpenShift v4.13 has certain major changes w.r.t. OVN CNI. The NSIC needed an enhancement to ensure compatibility and smooth operation within the specified environment, enhancing stability and performance. Users running on OpenShift v4.13+ with OVN CNI are encouraged to update to this release for continued support and seamless user experience.

Selective processing of the OpenShift Route resources

In our ongoing efforts to optimize the operation and efficiency of the NetScaler Ingress Controller (NSIC), we have introduced a significant update concerning how OpenShift Route resources are processed. Starting with this release, NSIC will now selectively process only those Route resources that are tagged with specific NSIC-associated labels. This update marks a departure from the previous approach where NSIC processed all Route resources within the OpenShift cluster indiscriminately.
To facilitate this new feature, users are required to specify a set of route labels during the installation of each NSIC instance. These labels can be defined using the routeLabels argument in the helm chart.
For example, if the helm chart release name is my-nsic, then the routeLabels associated with the NSIC would be proxy in (my-nsic).

For a Route resource to be recognized and processed by a specific NSIC instance, the route must include at least one of the provided routeLabels.

Assets 2
Loading