Skip to content

Release 2.0.6
Compare
Choose a tag to compare
@subashd subashd released this 20 Aug 13:15
· 8 commits to master since this release
2.0.6
5170766

Version 2.0.6

What's new

Support for 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. The load-balanced applications can be either the same application, different applications of the same domain, or entirely different applications.

Earlier, to load balance applications in multiple clusters, a dedicated content switching virtual server was required on NetScaler for each instance of NetScaler Ingress Controller (NSIC) running in the clusters. With NetScaler multi-cluster ingress solution, multiple ingress controllers can share a content switching virtual server. Therefore, applications deployed across clusters can be load balanced using the same content switching virtual server IP (VIP) address. For more information, see Multi-cluster ingress.

New parameters within ConfigMap

The parameters metrics.service and transactions.service parameters are added under the endpoint object for analytics configuration using a ConfigMap.

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

    Note:

    The metrics.service parameter replaces the server parameter starting from NSIC release 2.0.6.

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

    Note:

    The transactions.service parameter replaces the service parameter starting from NSIC release 2.0.6.

You can now change all the ConfigMap settings at runtime while NetScaler Ingress Controller is operational.

Fixed issues

  • Sometimes, the content switching virtual servers in NetScaler are deleted because of a Kubernetes error. Meanwhile, when NetScaler Ingress Controller (NSIC) restarts, it looks for the content switching virtual servers in NetScaler and because those servers are not found, NSIC remains in the reconciliation loop. With this fix, NSIC no longer looks for the content switching virtual servers in NetScaler and proceeds with further configuration.
Assets 2
Loading