Skip to content

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

Compare
Choose a tag to compare
@subashd subashd released this 20 Aug 13:14
· 5 commits to master since this release
1ee3dd9

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>.