Helm chart release notes for NetScaler Ingress Controller and GSLB Controller 1.41.5
This release note contains information about the Helm chart-related changes for the NetScaler Ingress Controller and GSLB controller version 1.41.5.
What's new
Automated Custom Resource Definitions (CRDs) installation using Helm
Earlier, CRDs installation was managed by specifying the crds.install
parameter in the NSIC helm install
command. If crds.install=true
was specified, CRDs would be installed; if omitted, the CRD installation was skipped. If crds.install=true
was specified in the NSIC helm install
command and the cluster already had a CRD installed, the NSIC installation failed. Therefore, to specify the correct value for crds.install
parameter, you had to know the status of the CRD installation in each cluster in your environment. Moreover, in an environment with multiple clusters, the process of updating the parameters became cumbersome and led to human error.
With this enhancement, Helm manages the CRD installations during the NSIC installation. When you run the NSIC helm install
command, CRDs will be installed with NetScaler ingress controller via Helm automatically, if CRDs are not already installed in the cluster. If the CRDs already exist, the CRDs installation is skipped with a warning. Additionally, If you wish to skip the CRDs installation, you can specify the --skip-crds
flag. For more information about this option in Helm, see here.
Fixed issues
- The Helm chart's template function to populate the analytics server's IP address uses the 'first' and 'lookup' methods. However, if the lookup method returns "None", the first method fails with a "nil pointer dereference" error. The template function is enhanced to handle such a corner case.