Helm chart release notes for NetScaler ADM Agent version 141.25.33

This release note contains information about the Helm chart-related changes for the NetScaler ADM Agent version 141.25.33.

What's new

• Support of configurable values for limits/resources
  ADM Agent Helm chart now supports configuring limits/resources values at the POD level as every pod has different functionalities and so CPU and memory consumption can vary accross different pods.

• Support of configurable values for liveness/readiness probe
  ADM Agent Helm chart now supports configuring liveness probe and readiness probe parameteres for CORE and REDIS pods. Similary liveness probe is added for LIC pod.

• Support of configurable values for HPA
  ADM Agent Helm chart now supports configurable values of CPU & Memory threshold values for HPA.

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.

Helm chart release notes for NetScaler Ingress Controller version 1.40.12

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

What's new

Support to bind SNI SSL certificate to NetScaler

NetScaler Ingress Controller (NSIC) now accepts defaultSSLSNICertSecret parameter using which you can provide a secret that is used to configure SSL SNI certificate on NetScaler for HTTPS ingresses and routes.

For example: defaultSSLSNICertSecret: <SECRET_NAME>.
SECRET_NAME: Name of the secret that has been deployed in the same namespace as that of NSIC.

Support for namespace-specific NSIC in OpenShift

NSIC can now be deployed at the namespace level in the OpenShift cluster. In this deployment mode, NSIC processes resources pertaining to the given namespace instead of managing all the resources across the entire cluster.

Note:

If NSIC requires access to clusterwide resources such as config.openshift.io, network.openshift.io, etc., it must be deployed with ClusterRole privileges.

ImagePullSecret support for GSLB Controller

The GSLB controller Helm chart now supports the imagePullSecret option that ensures smooth integration with container registries that require authentication. Before deploying the Helm chart, you must ensure the corresponding Kubernetes secret is created within the same namespace to enable seamless image pull during helm installation.

Helm chart release notes for NetScaler Ingress Controller version 1.39.6

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.

Helm chart release notes for NetScaler Observability Exporter version 1.9.001

This release note contains information about the Helm chart-related changes for NetScaler Observability Exporter 1.9.001.

Enhancements

Support for DEBUG severity level

The parameter nsoeLogLevel now supports DEBUG severity.

Support to export Auditlogs and Events to Kafka

Introduced new parameters kafka.events and kafka.auditlogs, which can be set to yes for exporting auditlogs and events to Kafka. You must set the timeseries.enabled parameter to true to enable this export.

Fixed issues

• Fixed a data loss issue with Splunk export over SSL. As part of the fix, a new field ConnectionPoolSize is introduced. ConnectionPoolSize and MaxConnections can be used to control the rate at which data is exported. For specifics of these fields, see Description of configuration parameters.
• Multiple NSOE instances cannot be deployed within the same Kubernetes/ OpenShift namespace. This has been fixed in this release.

Helm chart release notes for NetScaler Ingress Controller version 1.38.27

There is no change in parameters in this Helm Chart release. The default value of NSIC image in Helm Chart is now 1.38.27.
For more details about this NSIC release, please refer this

Helm chart release notes for NetScaler CPX with Ingress Controller version 1.37.6

This version of helm chart contains NetScaler CPX version 13.1-51.15.

Fixed issues

• Fixed helm template issue in the charts.

Helm chart release notes for NetScaler ADM Agent version 141.16.37

This release note contains information about the Helm chart related changes for the NetScaler ADM Agent version 141.16.37.

What's new

Improved logging for ADM Agent Pod.

Helm chart release notes for NetScaler Ingress Controller version 1.37.5

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

Enhancements

• Earlier, the global server load balancing (GSLB) site configuration had to be done manually. Now, the global server load balancing (GSLB) site configuration on NetScaler is done automatically. The following new parameters are added for the NetScaler GSLB Controller Helm Chart:
  -adcCredentialSecret: Specifies the secret key to log on to the NetScaler VPX or MPX.
  -secretStore.enabled: When you want to deploy other secret provider classes, set this parameter to "True".
  -secretStore.username: The SecretStore username. The username is fetched from the secret provider if secretStore is enabled.
  -secretStore.password: The SecretStore password. The password of NetScaler is fetched from the Secret Provider if secretStore is enabled.
  -nsIP: The IP address of the NetScaler device.
  -sitedata[0].sitePublicip: The public IP address of the first GSLB site.
  -sitedata[0].siteMask: The netmask of the first GSLB site IP address.

Fixed issues

• When multiple ingress controllers coexist within a cluster and the ingress class specified for a controller is switched to another controller, the newly associated NetScaler Ingress Controller does not update the ingress status correctly. This issue is fixed.

Known issues

• When the Helm chart of a NetScaler Ingress Controller is uninstalled, the ingressclass resource associated with the chart gets deleted. Hence, some configuration might be deleted because of the deletion of ingressclass.

Workaround:

1. Add the annotation "helm.sh/resource-policy": keep in the ingressclass resource definition.
2. Uninstall the helm chart using the helm uninstall command.
3. Delete the ingressclass resource manually.

Helm chart release notes for NetScaler Observability Exporter version 1.8.001

What's new

Support to enable logging

Now, you can enable container logging on NetScaler Observability Exporter according to different severity levels. These logs are helpful to monitor and troubleshoot NetScaler Observability Exporter deployments.
A new parameter coe.nsoeLogLevel is introduced in the Helm chart to configure logging.
For more information, see the NetScaler Observability Exporter documentation.

Fixed issues

• NetScaler Observability Exporter occasionally stops sending data to Splunk under low traffic conditions. This issue is fixed now.
• For Kafka deployments, the AVRO schema is showing null values. This issue is fixed now.