Release 2.1.0

This release notes document describes the enhancements and changes, fixed and known issues that exist for release 2.1.0

NetScaler® Kubernetes Gateway Controller release 2.1.0

What’s new

Exposing a TCP/UDP application by using Gateway and TCPRoute/UDPRoute CRDs

NetScaler Kubernetes Gateway Controller supports exposing a TCP/UDP-based application by using the Kubernetes Gateway API with NetScaler.

For more information, see Deploy NetScaler Kubernetes Gateway Controller and Deploy NetScaler CPX Kubernetes Gateway Controller.

Fixed issues

-  WebSocket is disabled by default. You can now use the HTTPProfile CRD for this use case.

-  Issues observed in the HTTPProfile CRD controller when GatewayClass is provided in the profile. The GatewayClass name provided in the profile might cause no attribute ‘ref_manager’ error.

-  Host names are not getting the correct precedence over wildcards when they share the same parent domain. As a fix for this issue, routing priority for overlapping host names on the same content switching virtual server is enhanced.

-  RequestHeaderModifier.set works only if the header already exists.

-  URLRewrite.replacePrefixMatch produces double slashes, and therefore path normalization is not handled correctly.

-  Any two HTTP Routes whose names are the same up to 20 characters create one load balancing virtual server instead of two. Conflicts are observed in load balancing virtual server naming.

-  Load balancing virtual server service group binding is lost after controller restart or service event is received after the HTTP route.

-  During GET calls to the Kubernetes API, the 429 errors are observed.

Helm chart release

For information on Helm chart release, see Helm Chart Release Notes.

Release 2.1.0