Release 2.0.0
This release notes document describes the enhancements and changes, fixed and known issues that exist for release 2.0.0
NetScaler® Kubernetes Gateway Controller release 2.0.0
What’s new
Using pre-configured certificates with NetScaler Kubernetes Gateway Controller
You can now use certificates or certificate bundles that are already configured on your NetScaler appliance with your Kubernetes Gateway. This feature simplifies certificate management by allowing you to reference existing certificates instead of managing them as Kubernetes Secrets.
For more information, see Using pre-configured certificates with NetScaler Kubernetes Gateway Controller.
Support to establish a network between Kubernetes nodes and the NetScaler instance outside the Kubernetes cluster
For seamless functioning of services deployed in a Kubernetes cluster, the Ingress NetScaler device must reach the overlay network where Pods run. You can get this connectivity in one of the following ways:
-
Enable automatic route configuration in the NetScaler Kubernetes Gateway Controller.
Set gatewayController.nodeWatch: true in the controller spec to create routes on NetScaler for each Pod subnet.
Note:
You can use this option when the NetScaler SNIP address shares the same subnet as the Kubernetes nodes.
-
Deploy a NetScaler Node Controller to drive subnet routes from Kubernetes nodes.
Note:
gatewayController.nodeWatchisfalseby default.
For more information, see Establish a network between Kubernetes nodes and NetScaler instance outside the Kubernetes cluster.
NetScaler Kubernetes Gateway controller does not add the backend service group binding when a RequestMirroring filter is defined in httproute.
Entity name change for CRDs
When a NetScaler Custom Resource Definition (CRD) instance is created, the NetScaler Kubernetes Gateway Controller generates multiple NetScaler entities associated with that CRD instance. The NetScaler Kubernetes Gateway Controller maintains unique names for each entity to preserve its association with the CRD instance. Since entity naming is based directly on CRD names, some NetScaler entity names exceeded the maximum character limit.
Starting with NetScaler Kubernetes Gateway Controller 2.0.0, the naming convention is optimized by using the following approach to generate shorter entity names during CRD creation:
- Hashed naming: A portion of the entity name is hashed to reduce the overall length
- Preserved information: The necessary Kubernetes related metadata is retained in the entity’s comment field, if the entity comment is supported by NetScaler
- Improved compatibility: Names comply with NetScaler character restrictions while maintaining full traceability
For more information, see Entity name change for CRDs.
Helm chart release
For information on Helm chart release, see Helm Chart Release Notes.