Helm chart release notes for NetScaler Ingress Controller and GSLB Controller version 2.0.6

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

What's new

• The following Helm chart parameter has been added for the multi-cluster ingress solution. NetScaler multi-cluster ingress solution enables NetScaler to load balance applications distributed across clusters using a single front-end IP address. For more information on multi-cluster ingress, see Multi-cluster ingress.

  • multiClusterPrefix: Specifies the multi-cluster prefix for an NSIC instance that is part of the multi-cluster ingress setup. You must specify the same value for the multiClusterPrefix parameter for each NSIC instance that is part of the multi-cluster ingress setup. For a different set of NSICs in another multi-cluster ingress setup configuring the same NetScaler, the multiClusterPrefix value must be consistent across NSIC instances but different from the value used in the other set.

• The following Helm chart parameters have been added for analytics configuration using ConfigMap.

  • analyticsConfig.endpoint.metrics.service: Set this value as the IP address or DNS address of the observability endpoint.

  • analyticsConfig.endpoint.transactions.service: Set this value as the IP address or namespace/service of the NetScaler Observability Exporter service.

    Notes:

    • Starting from NSIC release 2.0.6, analyticsConfig.endpoint.metrics.service replaces analyticsConfig.endpoint.server.
    • Starting from NSIC release 2.0.6, analyticsConfig.endpoint.transactions.service replaces analyticsConfig.endpoint.service.
    • If you are upgrading from any NSIC Helm chart version 1.x to 2.x, note down the metrics_endpoint (analyticsConfig.endpoint.server) and transactions_endpoint (analyticsConfig.endpoint.service) values, and then upgrade using the following set parameters in Helm upgrade: --set analyticsConfig.endpoint.metrics.service=<metrics_endpoint>,analyticsConfig.endpoint. transactions.service=<transactions_endpoint>.

Helm chart release notes for NetScaler ADM Agent version 141.31.38

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

What's fixed

• HPA is disabled for ADM Agent Core Container.

Helm chart release notes for NetScaler Ingress Controller and GSLB Controller version 1.43.7

This release note contains information about the Helm chart-related changes for NetScaler Ingress Controller (NSIC) and GSLB Controller version 1.43.7

What's new

• You can now enable and configure Liveness and Readiness probes for NSIC using the following Helm chart variables:

  • enableLivenessProbe (optional): Enables Liveness probe for NSIC and CPX. Configurable values are True and False. enableLivenessProbe is set to True by default.
  • enableReadinessProbe (optional): Enables Readiness probe for NSIC. Configurable values are True and False. enableReadinessProbe is set to True by default.
  • enableStartupProbe (optional): Enables Startup probe for CPX. Configurable values are True and False.
    enableStartupProbe is set to True by default.
  • readinessProbe (optional): Enables you to configure the settings for Readiness probe. You can configure the following parameters: initialDelaySeconds, periodSeconds, failureThreshold, and successThreshold. For information about these parameters, see Kubernetes documentation.
  • livenessProbe (optional): Enables you to configure the settings for Liveness probe.
  • startupProbe (optional): Enables you to configure the settings for Startup Probe.

• For NSIC and GLSB controller OpenShift deployments, DeploymentConfig objects are replaced with Deployment objects. Also, spec.strategy has been removed.

Helm chart release notes for NetScaler Ingress Controller 1.42.12

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

What's new

You can now add a hostname to a CPX instance deployed in Kubernetes or OpenShift cluster using the new hostname Helm chart parameter for NetScaler CPX with NetScaler Ingress Controller.

• hostName: Specifies the hostname for a CPX instance.

Helm chart release notes for NetScaler IPAM Controller 1.2.0

This release note contains information about the helm chart related changes for the NetScaler IPAM Controller version 1.2.0

What's new

• A new variable reuseIngressVip has been introduced. Using this variable, you can configure the IPAM controller to assign a different IP address to each ingress resource referring to the same VIP range.

Helm chart release notes for NetScaler Node Controller version 2.2.14

This release has multiple bug fixes in the NetScaler Node Controller Helm Chart.

What's fixed

• Incorrect references are fixed in the template functions and values.yaml.

The version of NetScaler Node Controller image 2.2.12 has not changed in this release.

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.